get-schema

Get Schema

This skill wraps the getSchema MCP tool. Use it to discover Intelligo's GraphQL types and fields before authoring a query.

When to use

• The user asks "what data is available?", "what fields does X have?", "what arguments does Y take?".
• You are about to call queryIntelligo and are uncertain about a type's shape.
• You need to disambiguate which entry point on Query fits the user's request.

Two modes

1. Single type (cheap, recommended). Pass typeName to fetch one type's SDL.

   getSchema(typeName: "Search")
   

   Returns ~50–500 tokens depending on the type.

2. Full SDL (expensive — use sparingly). Call with no arguments.

   getSchema()
   

   Returns ~12k tokens of the entire schema. Only do this if the user explicitly asks for the whole schema, or you genuinely need to scan many types.

Workflow

1. Identify the smallest type that answers the user's question.
2. Call getSchema with typeName: "<that type>".
3. If the type references other types you need, call getSchema again per dependency rather than fetching the full SDL.
4. Once you have enough shape info, hand off to the query-intelligo skill (or call queryIntelligo directly) to fetch actual data.

Common types to inspect

• Query — entry points.
• Search, Project, Subject, Finding — core domain objects.
• Viewer, Org — auth context.

Tip

GraphQL introspection (__schema, __type) also works inside a queryIntelligo call. For one-off field lookups during query composition, that is sometimes cheaper than a separate getSchema round-trip.