Skip to main content
Glama

Verified place shortlist — Atom

Verified place shortlist

verified_place_shortlist
Read-onlyIdempotent

Submits a verified place shortlist record (constraint declarations, declared criterion rows, declared place rows with declared verification evidence, evaluation declarations, ranking declarations, freshness and uncertainty handling declarations, red lines) and returns a deterministic VERIFIED_PLACE_SHORTLIST_SOUND / VERIFIED_PLACE_SHORTLIST_NOT_SOUND / INSUFFICIENT_EVIDENCE verdict across six sections, including computed criterion-to-place coverage, per-row evidence completeness and winner and backup resolution checks over the declared rows, with per-check evidence. Audits the declared shortlist record only; it fetches nothing live, verifies no real-world fact and recommends or books nothing. The word verified in its name refers to the caller's declared verification discipline, not to any live verification by the atom.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verified_place_shortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
placesNoDeclared place rows.
rankingNoRanking evidence.
criteriaNoDeclared criteria rows.
handlingNoHandling evidence.
red_linesNoRed lines evidence.
evaluationNoEvaluation evidence.
constraintsNoConstraints evidence.
shortlist_titleNoShortlist under review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, and the description adds substantive behavior beyond them: deterministic verdicts with three named outcomes, evaluation across six sections, computed coverage and per-row evidence-completeness checks, and explicit confirmation that nothing live is fetched or booked. With no output schema present, spelling out the verdict vocabulary is essential and it does so.

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?

The structure is front-loaded: what is submitted, what comes back, then the scope disclaimers. The opening sentence is a very long parenthetical enumeration and the word 'declared' recurs heavily, but each clause carries information rather than 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?

For an eight-parameter nested-object tool with no output schema, the description supplies the return-value semantics and the computational behavior an agent needs to interpret results. It stops short of explaining how the verdict is reached per section or noting that no parameters are required, but the SERVICE.md pointer covers the deeper field detail.

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%, so the eight parameters are already documented; the description's enumeration of sections (constraints, criteria, places, evaluation, ranking, handling, red lines) largely mirrors the parameter names rather than adding row-level or format meaning. The one genuinely additive note is that place rows carry 'declared verification evidence', and it defers row schemas to SERVICE.md.

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?

The description names a concrete verb ('submits') and a concrete resource (a verified place shortlist record), enumerates the record's sections, and states the exact return artifact (VERIFIED_PLACE_SHORTLIST_SOUND / NOT_SOUND / INSUFFICIENT_EVIDENCE). It also pre-empts the most likely misreading by clarifying that 'verified' refers to the caller's declared discipline, not live verification.

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?

It clearly bounds the scope of use: 'Audits the declared shortlist record only; it fetches nothing live, verifies no real-world fact and recommends or books nothing.' That is real when-not guidance against expecting live lookups or booking. What is absent is a positive 'call this when...' trigger sentence or any named alternative tool for the live-verification case.

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.