Skip to main content
Glama

silex_suggest_entities

Autocompletes verified entities such as tickers, CVEs, ICAOs, NCTs, and solicitations, plus indexed JSON schema keys, from a prefix to help users find valid identifiers.

Instructions

Autocomplete verified entities (tickers, CVEs, ICAOs, NCTs, solicitations) and JSON schema keys currently indexed in With Silex.

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
prefixYesPrefix to autocomplete, e.g. cve, nvda, kbos, xno

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 does disclose meaningful behavioral context: results are "verified" (canonical, not free-form matches) and only cover what is "currently indexed in With Silex," which warns the agent that coverage is bounded by the index. It says nothing about matching semantics (prefix vs. substring, case sensitivity), result count/format, or rate limits.

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

Conciseness5/5

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

A single dense sentence, front-loaded with the verb and resource, with no filler. Every clause (verified entities, the category list, JSON schema keys, index scope) contributes distinct information.

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?

For a simple one-parameter read tool this covers purpose and data scope adequately, but with no output schema and no annotations the description leaves the return shape undocumented — an agent cannot tell whether it receives a list of strings, objects with IDs, or ranked suggestions.

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

Parameters4/5

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

Schema description coverage is 100% with a documented single parameter and inline examples, so the baseline is 3. The description adds value beyond the schema by enumerating the entity categories the prefix can resolve into (tickers, CVEs, ICAOs, NCTs, solicitations, JSON schema keys), telling the agent what kinds of identifiers a valid prefix maps to.

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?

Names a specific verb ("Autocomplete") and a concrete resource set ("verified entities ... and JSON schema keys"), plus parenthetical examples of entity families (tickers, CVEs, ICAOs, NCTs, solicitations) that make the domain unambiguous. It does not differentiate itself from the listed siblings, so it stops short of a 5.

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?

The verb implies the usage context (partial-string lookup to resolve a canonical identifier), but there is no explicit when-to-use / when-not-to-use statement and no mention of alternatives such as silex_hyper_search for full-text lookup. Guidance is inferable rather than stated.

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