Skip to main content
Glama

get_function_detail

Source + uncovered lines for one function. The agent typically calls this after list_untested_functions to pick a target and write tests for it directly without going through the prompt generator.

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": {
      "function_id": "<function_id>"
    },
    "name": "get_function_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
function_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the return content (source and uncovered lines) and the workflow position, but says nothing about read-only safety, error behavior for an invalid function_id, or output size/format.

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?

Two short sentences, front-loaded with what is returned, followed by the workflow hint. The awkward line wrapping is cosmetic and no sentence is wasted.

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

Completeness4/5

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

For a simple one-parameter read tool with no output schema, the description covers what comes back and when to call it. The main residual gap is the function_id format, which is left to inference.

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 0% for the single function_id parameter, so the description must compensate. It implies the id comes from list_untested_functions, which is useful, but it never states the expected format or whether it is a name, path, or opaque id.

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 resource and payload: source code plus uncovered lines for a single function. It also names the sibling it follows (list_untested_functions), which helps an agent place it in the workflow, though it does not explicitly contrast with the prompt-generator siblings.

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

Usage Guidelines4/5

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

It gives a clear usage context: call this after list_untested_functions to pick a target and write tests directly, bypassing the prompt generator. That implicitly routes the agent away from get_generated_prompt/get_baseline_prompt, but the exclusion is only implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources