Skip to main content
Glama

issues

Lists open problems detected by Strata's checks, most severe first, so agents can identify stratigraphic contradictions and record conflicts by site or problem kind.

Instructions

Open problems found by the checks, most severe first.

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": "issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
siteNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/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 usefully discloses that only open problems are returned and that they are sorted most severe first, but says nothing about read-only safety, pagination, whether limit is a maximum, or how filtering by kind and site affects results.

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, front-loaded sentence with no wasted wording. The ordering constraint is stated immediately, which is exactly the kind of detail an agent needs before invoking a list tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values need not be explained, but the tool has three filter parameters with zero schema coverage and no annotations. The description is too thin to tell an agent what 'checks' are, what the kind values mean, or what site filtering does.

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?

Schema description coverage is 0%, so the description must compensate for the three undocumented parameters. It adds no meaning for kind, site, or limit; the enum values are somewhat self-descriptive but domain-specific terms like 'cut_or_cover' and 'period_inversion' remain unexplained.

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 clearly identifies the resource as open problems found by checks and states the ordering (most severe first). It lacks an explicit verb and does not name a sibling alternative, but an agent can still tell this returns a prioritized issue list rather than explanations or history.

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 guidance on when to call this tool versus siblings such as explain_issue, recheck, or overview. The phrase 'open problems found by the checks' implies a listing context, but no exclusions or alternatives are stated.

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