Skip to main content
Glama

mocop

suggest

Read-only

Prefix suggestions for organizations and entities.

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": {
      "query": "<query>"
    },
    "name": "suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds nothing beyond that: no note on how many suggestions come back, whether matching is case-insensitive, or what happens on empty/no-match input, which is the kind of context expected for a lookup tool with no output schema.

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

Conciseness3/5

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

One short sentence with no filler and the purpose front-loaded, which is efficient. However, the brevity comes at the cost of under-specification rather than serving conciseness, so it does not earn a top score.

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?

With one undocumented parameter, no output schema, and no explanation of result shape or limits, the definition does not give an agent enough to invoke this confidently. For a suggestion/autocomplete tool the description should at minimum clarify prefix semantics and expected return behavior.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter `query`, so the schema supplies no meaning. The description does not say whether `query` is a bare prefix string, a minimum length applies, or whether it must match the start of the name versus anywhere in it, leaving the only real parameter undocumented.

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 a resource (organizations and entities) and an operation (prefix suggestions, i.e. autocomplete-style matching), but 'suggestions' is soft and the phrasing leaves it unclear whether it returns whole records, names only, or ranked matches. Nothing in the text distinguishes it from siblings like browse_organizations or get_entity, so an agent must infer the difference.

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 guidance: no statement that this is for partial-name/prefix lookups before the full name is known, no exclusion of the exact-lookup siblings, and no prerequisites. The agent must guess the trigger condition from the tool name alone.

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