Skip to main content
Glama

entry_candidates

Documents, booked invoices, open items one movement may pay; link one, then settle_entry.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "entry_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It does not say whether the tool is read-only, what it returns, whether linking has side effects, or what permissions are needed; only a vague workflow hint is given.

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

Conciseness2/5

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

It is very short, but the fragment is cryptic and not front-loaded with a clear verb. Brevity comes at the cost of understanding.

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 one-parameter tool with no annotations or output schema, the description should at least explain the candidate list and entry_id. It leaves the return shape, linking step, and parameter meaning unclear.

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

Parameters1/5

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

The sole parameter entry_id is undocumented in both schema (0% coverage) and description. The phrase 'one movement' may hint at the entry, but it does not explain the expected ID or format.

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

Purpose3/5

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

The description names the resource (documents, booked invoices, open items) and hints at a workflow with settle_entry, but it never states the action explicitly (list/retrieve candidates) and reads as a sentence fragment.

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?

It implies this tool is used to choose a candidate before calling settle_entry, which is useful sequencing. It does not state when not to use it, prerequisites, or alternatives beyond the next-step hint.

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