Skip to main content
Glama
Sign In
Courtship

Courtship

by grimmdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

call_tool

Invoke any Courtship tool through a proxy with automatic response compression and shaping, helping AI assistants inspect LÖVE game data without overload.

Instructions

Invoke any tool through the proxy with automatic response compression and shaping.

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>",
      "arguments": "<arguments>"
    },
    "name": "call_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe target tool name
argumentsYesTool parameters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: responses are automatically compressed and shaped. However, that phrase is left undefined — it is unclear whether output is truncated or reformatted and whether information is lost — and there is no mention of error behavior, permissions, or rate limits for a tool that can invoke arbitrary operations.

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 no filler. It is efficient, though its brevity is partly the cause of the missing guidance noted elsewhere.

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

Completeness2/5

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

For a generic proxy that can invoke any tool, with no annotations, no output schema, and a nested free-form arguments object, the description is thin. An agent gets no workflow context (discover → load schema → call), no description of the compression/shaping contract, and no failure semantics.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents both parameters (target tool name and tool parameters). The description adds no meaning beyond that — it does not say that `arguments` must conform to the target tool's own schema, which would be the one genuinely useful clarification for a nested object parameter.

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?

The description states a specific verb and resource (invoke any tool through the proxy) and adds a distinguishing trait (automatic response compression and shaping). It never mentions its siblings discover_tools or load_tool_schema, so an agent cannot tell from the description alone whether it must first discover/load a schema before calling this.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as resolving the target tool name via discover_tools or load_tool_schema, and no indication of what happens on invalid tool names. The agent must infer the entire workflow from the sibling list.

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