Skip to main content
Glama

silex_suggest_entities

Read-onlyIdempotent

Instant autocomplete of live indexed tickers, CVEs, airport ICAOs, NCTs, and JSON schema field names.

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": {
      "prefix": "<prefix>"
    },
    "name": "silex_suggest_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixYes2+ character prefix to autocomplete live indexed stock tickers, CVE IDs, airport ICAOs, NCT trial IDs, and schema fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / prefix / description
      Added value: +"2+ character prefix to autocomplete live indexed stock tickers, CVE IDs, airport ICAOs, NCT trial IDs, and schema fields."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the useful fact that the index is 'live', meaning results reflect currently indexed entities, but says nothing about result limits, empty-result behavior, or ranking.

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 filler, and the verb comes first. It is efficient but nearly minimal — the same one line is all the description provides.

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?

With one parameter, rich annotations, and no output schema, the description would ideally state what comes back (a list of matching names? scored?), since no output schema documents the return value. As written it is adequate to invoke but leaves the response shape and result caps 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 100% and the single parameter's schema text already states the 2+ character prefix rule and lists the same entity families. The description's enumeration of entity types marginally reinforces what a prefix matches, but adds no syntax, format, or case-sensitivity detail beyond the schema.

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 ('autocomplete') combined with an enumerated set of entity families (tickers, CVEs, ICAOs, NCTs, schema fields), so an agent knows exactly what pool is being completed. It does not explicitly contrast itself with siblings like silex_hyper_search or silex_encyclopedia_lookup, so the differentiation is inferable rather than stated.

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; 'Instant' implies a cheap prefix-completion call but nothing tells the agent to call this before a search or lookup, or what to do with a partial match. The only actionable constraint (2+ characters) is carried by the schema, not the description.

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.