Skip to main content
Glama

Lattice

by io.namiq
OverviewDiscussionsAdmin

Search ids by prefix

graph_search
Read-onlyIdempotent

List nodes whose external id starts with a prefix (e.g. CVE-2024-1, T105). Ids only, not free text. If the answer has truncated: true, pass its next_cursor as cursor to continue; a list without truncated is complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoOptional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones.
limitNoMaximum items to return. The server clamps it to its own maximum; the answer reports applied_limit and limit_clamped.
cursorNoContinuation token: pass the next_cursor from a previous answer that had truncated: true to get the next page. Omit it for the first page.
id_prefixYesStart of an external id, at least a few characters, for example CVE-2024-1 or T105. Not free text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Continuation token: pass the next_cursor from a previous answer that had truncated: true to get the next page. Omit it for the first page."
    • addedInput schema / properties / id_prefix / description
      Added value: +"Start of an external id, at least a few characters, for example CVE-2024-1 or T105. Not free text."
    • addedInput schema / properties / label / description
      Added value: +"Optional node label (type) to restrict the answer to, for example CVE, Technique or Detection. The valid labels are listed by graph_meta; an unknown label is refused with the valid ones."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items to return. The server clamps it to its own maximum; the answer reports applied_limit and limit_clamped."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds return-behavior semantics that annotations can't: the meaning of 'truncated: true' and that its next_cursor must be passed back, and that a result without truncated is complete. That is genuine value, though it doesn't cover rate limits or permissions.

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?

Three tightly written sentences: what it returns, what it is not, and how to paginate. Front-loaded purpose with zero filler.

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?

With no output schema, the description usefully explains the truncated/next_cursor contract, which is the key thing an agent needs to loop correctly. It stops short of naming the returned id field or showing a full envelope, so a small gap remains.

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 description coverage is 100%, so label, limit, cursor, and id_prefix are already documented in the schema, including the graph_meta cross-reference and clamping behaviour. The description largely restates the cursor/id_prefix semantics, so the baseline of 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ('List nodes whose external id starts with a prefix') with concrete id examples, and explicitly bounds the scope with 'Ids only, not free text.' This clearly separates it from sibling search/lookup tools.

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?

Gives the triggering condition (prefix of an external id) plus an explicit exclusion ('not free text'), and explains when to use the cursor. It doesn't name an alternative sibling for the free-text case, which keeps it short of a 5.

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

All Lattice toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources