Skip to main content
Glama

list_low_confidence_fields

Identify which extracted fields require human review and see the reason for each flag. Use a document ID to route low-confidence extraction results to reviewers.

Instructions

List the fields of a stored extraction that need human review, and why.

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": {
      "document_id": "<document_id>"
    },
    "name": "list_low_confidence_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that reasons are returned alongside fields, which is useful, but says nothing about what threshold defines 'low confidence', whether an empty result is possible, ordering, or the safety/permission profile of the call.

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 tight sentence with the key information front-loaded and no filler. It could be marginally improved by placing the identifier requirement before the outcome, but nothing is wasted.

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?

The tool is simple and an output schema exists, so return format need not be explained. However, the one required parameter is undocumented in both schema and description, and the 'low confidence' criterion is undefined, leaving a meaningful gap for a review-oriented tool.

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

Parameters2/5

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

There is one parameter, document_id, at 0% schema description coverage, and the description never mentions it. It refers only to 'a stored extraction', leaving the agent to guess that document_id is the identifier used to locate that extraction.

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?

The description uses a specific verb ('List') plus a precisely scoped resource: fields of a stored extraction that need human review. That scope distinguishes it implicitly from siblings like get_extraction, though it never names an alternative explicitly.

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 explicit statement of when to call this versus get_extraction or extract_document, and no prerequisites or exclusions. The phrase 'need human review' hints at a review workflow but the agent must infer the condition that selects this tool.

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