Skip to main content
Glama
Sign In
Hermai MCP

Hermai MCP

Official
by hermai-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Check schema request status

check_schema_request_status
Read-onlyIdempotent

Retrieve the status of a previously submitted schema request using its ID to see if it has been processed.

Instructions

Check the status of a previously submitted Hermai schema request. Read-only.

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": {
      "request_id": "<request_id>"
    },
    "name": "check_schema_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesSchema request id returned by submit_schema_request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds 'Read-only', which is redundant. It does not provide additional behavioral context such as expected results or edge cases, so the value added is minimal.

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 wasted words. Every word earns its place, making it highly efficient for an AI agent to parse.

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 simple read-only check with one parameter and no output schema, the description is mostly complete. However, it could be improved by mentioning what kind of status information is returned, though the absence of an output schema makes this less critical.

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?

The input schema has 100% coverage with a clear description for the single parameter 'request_id' ('Schema request id returned by submit_schema_request'). The tool description does not add further semantic value beyond what the schema already provides, so a baseline score is appropriate.

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 clearly states it checks the status of a previously submitted Hermai schema request. It uses a specific verb ('check') and resource ('schema request'), and distinguishes from siblings like 'submit_schema_request' (submission) and 'lookup_schema' (schema lookup).

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?

The description implies usage after submitting a request ('previously submitted'), providing clear context. However, it does not explicitly mention when not to use or suggest alternatives, which keeps it from a top score.

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