Skip to main content
Glama

enrollment_status

Poll the status of your own mentor enrollment request to check whether it is pending, accepted, or rejected.

Instructions

Poll the state of your own mentor enrollment request.

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

Input Schema

NameRequiredDescriptionDefault
request_idYes
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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 supplied, the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether this is strictly read-only, what states can be returned, whether polling is rate-limited, or what happens for an unknown request_id. "Poll" weakly implies a non-mutating read, but that is inference, not disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is good structure, but the brevity is under-specification rather than economy — the same one line could have carried the request_id origin without bloat.

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?

An output schema exists, so return values need not be explained, but for a two-parameter polling tool with zero annotation and zero schema coverage the description leaves the agent without the parameter meanings or behavioral guarantees it needs. It is too thin relative to the gaps in the structured fields.

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% for two parameters, so the description must compensate and does not. It never explains that request_id is the identifier returned by the request_mentor call, nor what actor_handle does or why it would be supplied for "your own" enrollment. Both parameters are effectively undocumented.

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 gives a specific verb ("Poll") and resource ("mentor enrollment request") plus a scope qualifier ("your own"), which separates it from the sibling request_mentor that presumably creates such a request. It stops short of naming that sibling or stating the distinction explicitly, so it is clear but not fully differentiated.

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?

"Poll" implies this is called repeatedly after a request exists, which hints at when to use it, but there is no explicit statement of prerequisites, no mention of how often to poll, and no named alternative for checking status another way. Usage is inferred rather than stated.

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