Skip to main content
Glama
Sign In
Theseus

Theseus

by ywapom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inspect_error

Reveals validation errors on a web page, optionally limited to a specific field or control, so you can identify why input was rejected.

Instructions

Reveal validation errors on the page, optionally for one field or control.

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

Input Schema

NameRequiredDescriptionDefault
targetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. While 'Reveal' implies a read-only inspection, the description does not explicitly confirm that it has no side effects, whether it requires prior form submission, or what happens when no errors exist.

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?

The description is a single, front-loaded sentence with no redundant or filler content. It communicates the core action and optional scoping efficiently.

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 has an output schema, so return values need not be explained. However, without annotations and with 0% schema description coverage, the definition leaves gaps around target format and read-only behavior that an agent might need before invoking it.

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 0%, so the description must compensate. It does clarify that the target parameter optionally scopes inspection to one field or control, but it does not specify how to identify that field/control (e.g., selector, label, or index).

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 states a specific verb and resource: reveal validation errors on the page. This clearly distinguishes the tool from generic page-reading or screenshot tools, though it does not explicitly name or compare against sibling tools such as assert_state or read_page.

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 phrase 'on the page' and the optional field/control targeting imply the tool is used to inspect validation errors after some interaction. However, there is no explicit guidance on when to use this versus assert_state, read_page, or screenshot, nor any exclusions.

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

Deploy Server

Other Tools