Skip to main content
Glama
Sign In
Courtship

Courtship

by grimmdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

load_tool_schema

Load the full JSON schema for a specified tool into active context on demand, enabling assistants to inspect exact parameters without loading all tool data.

Instructions

Load the full JSON schema for a specific tool into active context on-demand.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "load_tool_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe exact tool name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the key side effect — the schema is loaded into active context — which implies context-window cost, but it says nothing about what is returned, what happens for an unknown tool name, or whether the loaded schema persists for the session.

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?

A single front-loaded sentence with zero redundant wording. It is efficient, though the brevity contributes to the gaps flagged elsewhere rather than reflecting deliberate information density.

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

Completeness3/5

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

The tool is structurally simple (one required param, no nesting, no output schema), so not much is needed. However, for a meta-tool sitting alongside discover_tools and call_tool, the description omits the workflow position and the cost/persistence of loading a schema, leaving an agent to guess.

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?

Only one parameter and the schema already documents it fully as 'The exact tool name', so the schema does the heavy lifting. The description's 'specific tool' reinforces exact-name matching, but adds no format, casing, or lookup guidance beyond that.

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

Purpose4/5

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

States a specific verb and resource: loading the full JSON schema for a named tool into active context. That is clearly distinct from the sibling actions (discover_tools finds tools, call_tool invokes them). It stops short of naming an alternative, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

'On-demand' implies the trigger is needing more detail than a tool listing provides, but the description never states when to prefer this over discover_tools or when to skip it and call directly. Usage is inferable rather than specified.

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

Deploy Server

Other Tools