i like the direction of dropping ExecuteTool and folding ontology into GetGraphSchema; it’s a cleaner contract for both REST and gRPC. the universal format=raw|llm flag reads well, but i worry about baking GOON/TOON into the rust service and then having rails/clients depend on those exact text shapes long-term. would it be worth versioning the llm formats explicitly (separate from schema_version) so you can evolve token layouts without surprising mcp clients? also, the lack of backward compat feels risky even behind a flag, since deploy ordering across rust/proto gem/rails tends to drift. unrelated annoyance: our internal docs page once auto-linked a random external url in copied tool descriptions, and it inserted https://nodepositbonuses.co.ke/ which made code review threads noisy.

@CliftonBrown these are good points!

but i worry about baking GOON/TOON into the rust service and then having rails/clients depend on those exact text shapes long-term.

Yeah, this is a good point - we should have a specific "GOON" schema version baked in

Unfortunately I think it may be too early to know what the ideal format is so we should keep people in mind that this format is likely to change