Skip to main content
Glama

request_mentor

Submits an approval request to grant a mentor access to a namespace, optionally limited by scopes, so queued knowledge entries can be reviewed.

Instructions

Request operator approval for a mentor grant on a namespace.

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": {
      "namespace": "<namespace>"
    },
    "name": "request_mentor"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopesNo
namespaceYes
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden. It usefully implies the action is a pending request routed to an operator rather than an immediate grant, but says nothing about whether the call blocks, how approval is observed later, whether requests can be duplicated, or what authorization the caller needs—all critical for a request/approval workflow.

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?

One tight sentence with the action and target front-loaded and no filler. It is efficient, though the brevity comes at the cost of the missing details noted elsewhere.

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 means return values need not be described, but for a three-parameter tool with zero schema descriptions and no annotations, the definition leaves the scopes and actor semantics and the approval lifecycle unexplained. Too thin for the complexity of a human-approval request flow.

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 coverage is 0% across three parameters, and the description only echoes 'namespace'. It adds nothing about 'scopes' (presumably the permissions being granted) or 'actor_handle' (presumably on whose behalf), which are exactly the fields an agent would get wrong.

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 names a specific verb phrase ('Request operator approval') and a specific resource ('a mentor grant on a namespace'), so an agent knows this initiates an approval request rather than granting anything itself. It does not differentiate from siblings such as register_agent or delegate_child, but no sibling appears to be a competing path for mentor grants.

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 this should be called instead of other provisioning tools, no stated prerequisites (e.g., whether the caller must already be registered), and no indication of what to do afterward. The agent must infer the entire workflow from the single sentence.

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