Drillable

Describe a domain's tools

describe

Read-only

Discover the fleet's deeper machinery. No args → every mounted domain with its verbs grouped by rung (lookup → composability → contested → frontier). With domain → that domain's full tool list with descriptions and input schemas. Invoke anything it lists via call. Use this whenever the spine (lookup/search/verify) is too shallow for the question — e.g. "what can I make/patch/cover with MY inventory", contested claims, open questions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No	Optional: one domain's full tool schemas (e.g. 'cocktail').

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds context beyond the readOnlyHint annotation by explaining the two modes (no args vs domain) and that it returns tool lists with descriptions and schemas, which is non-destructive and informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and well-structured with two clear functional sections and usage guidance. Could be slightly shorter but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully complete for an informational tool with no output schema. Covers both invocation modes, usage context, and examples, leaving no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with the single optional parameter. The description adds value by explaining the behavior difference when domain is provided vs not, going beyond the schema's basic description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to discover deeper machinery by listing all domains or a specific domain's tools with schemas. It distinguishes itself from sibling tools like lookup and search by being for deeper exploration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'whenever the spine (lookup/search/verify) is too shallow for the question' and gives concrete examples like contested claims or open questions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Drillable tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Each tool has a distinct primary role—describe discovers, search/lookup/enumerate retrieve different shapes, compute aggregates, drill fetches addresses, verify checks claims, and notify_when_held tracks gaps. The main ambiguity is that compute and drill can both serve count/aggregate questions, though the descriptions do cross-reference each other to guide selection.

Naming Consistency4/5

Eight of the nine tools follow a clear lowercase single-word verb pattern: call, compute, describe, drill, enumerate, lookup, search, and verify. notify_when_held breaks that pattern with snake_case and a multi-word verb phrase, creating a minor but noticeable inconsistency.

Tool Count5/5

Nine tools is a well-scoped count for a knowledge retrieval and verification server. Each tool earns its place and the set avoids both bloat and thinness.

Completeness5/5

The tool surface covers the full intended lifecycle: discovery, search, glossary lookup, complete-set enumeration, aggregation, address-based drilling, claim verification, and registering unanswered questions. Abstentions and gap logging are built into misses, and describe/call unlock domain-specific verbs, so there are no obvious dead ends.

Resources

Need Help?