Skip to main content
Glama

Lodestar Stamp

by io.github.Banjo-Ventures
OverviewDiscussionsAdmin

List Covered Businesses

list_index
Read-onlyIdempotent

List businesses covered by a Lodestar Stamp draft record. Optional market reads that market's index; omitted reads the primary record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOptional next_cursor from the previous list_index answer on the same market. Omit for the first page; each page lists at most 50 businesses.
marketNoOptional market slug from list_markets, for example chicago-hvac. Omit for the primary index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Optional next_cursor from the previous list_index answer on the same market. Omit for the first page; each page lists at most 50 businesses.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / market
      Added value: +{
+  "description": "Optional market slug from list_markets, for example chicago-hvac. Omit for the primary index.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds that omitting market reads the 'primary record' and that a market reads that market's index, which is useful scoping context, but it says nothing about result volume, ordering, or what happens on an invalid slug.

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?

Two sentences, no padding, with the resource scope front-loaded and the parameter behavior stated second. Every clause earns its place.

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?

For a read-only list tool whose annotations cover the safety profile and whose schema is fully documented, this is nearly complete. The only gap is that no output schema exists and the description never characterizes the returned business entries, though pagination is covered in the cursor parameter.

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%, so the baseline is 3, but the description genuinely adds meaning beyond the schema: it clarifies that 'market' selects which index is read and that omission falls back to the primary record. That is the key behavioral consequence an agent needs to interpret the parameter.

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 and resource ('List businesses covered by a Lodestar Stamp draft record'), which an agent can distinguish from find_business or list_markets. The subject matter is domain-specific jargon, but the scope is precise enough to act on.

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 second sentence explains the effect of supplying 'market' versus omitting it, which implies usage, and the schema references list_markets as the source of the slug. However, there is no explicit statement of when to choose this tool over find_business or list_gaps.

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

All Lodestar Stamp 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