Skip to main content
Glama

Agent Onboarding

agent_onboarding
Read-onlyIdempotent

Configure this agent environment for Gryz after connecting, or explain how to use a Gryz capability. Read-only on Gryz and idempotent: each call returns one proposed action, a short report of what is already set up on this connection (live capabilities and token scopes), and a signed token to continue. If a follow-up call points at a step that has already moved on, earlier progress is kept and the current step is offered again; only a token that cannot be verified starts over. A proposed local-write action changes agent instruction files only after the client shows the targets and receives explicit user approval.

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

Input Schema

NameRequiredDescriptionDefault
focusNo
clientNo
answersNo
repo_pathNo
user_slugNo
git_remoteNo
continuationNo
acknowledged_action_idNo

Output Schema

NameRequiredDescriptionDefault
nextYes
statusYes
docs_urlYes
warningsNo
questionsNo
remainingYes
setup_stateYes
acknowledgedYes
continuationYes
contract_versionYes
registry_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Well beyond the annotations, it discloses the return shape (one proposed action, a setup report with live capabilities and token scopes, a signed continuation token), the idempotent-resume semantics including that only an unverifiable token restarts, and the approval gate before any local file write. The mention of local-write actions is consistent with readOnlyHint=true because the tool proposes rather than performs the write.

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?

Three sentences, front-loaded with the purpose and then the behavioral contract; each sentence carries distinct information (what it does, how state/resumption works, when writes are gated). The middle sentence is long and packs multiple clauses, but nothing is padding.

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?

With an output schema and rich annotations, the description does enough on returns and safety, but for a tool with 8 parameters, nested objects, and 0% schema coverage, the total absence of parameter guidance is a real gap an agent must guess through. Adequate at the behavior level, incomplete at the invocation level.

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?

Eight parameters, nested client/answers objects, enums, and 0% schema description coverage, yet the description names none of them. Only oblique hints exist — "signed token to continue" gestures at continuation and "agent instruction files" at config_targets — leaving focus, client.filesystem, answers, repo_path, user_slug, git_remote, and acknowledged_action_id unexplained anywhere.

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 concrete dual verb+resource: "Configure this agent environment for Gryz after connecting, or explain how to use a Gryz capability." That is clearly distinct from every sibling (document/note/task/poll CRUD), so an agent can identify it without opening the schema, though the mixed two-mode purpose is slightly abstract.

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?

It gives clear triggering context — call it "after connecting" or when the user wants a Gryz capability explained — and the resumption rule tells the agent it can safely re-call with an older token. It stops short of naming explicit when-not conditions or pointing to other tools for the non-onboarding cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.