Skip to main content
Glama

Agenturo

Draft a new public AI agent

draft_agent
Read-only

Prepare a new public AI agent from a name and a description of who or what it represents and what it should do — a person, brand, product, business, character, coach or specialist. Checks that its address (handle.agenturo.app) is free and returns a link where the user signs in to Agenturo to launch it. Nothing is created or reserved until they do.

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": {
      "name": "<name>",
      "description": "<description>"
    },
    "name": "draft_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe agent's display name, usually the person, brand or product it represents.
handleNoPreferred address, 5–15 lowercase letters or digits (becomes handle.agenturo.app). Derived from the name when omitted.
descriptionYesWho or what the agent represents, who it talks to, what it should help them with, and how it should sound.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that the tool performs a handle-availability check, returns a sign-in link rather than a created entity, and that no state is created or reserved. That reconciles nicely with readOnlyHint=true and destructiveHint=false. It does not address repeated invocation, which matters given idempotentHint=false.

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?

Two sentences, front-loaded with the action and ending with the crucial no-commitment guarantee. The mid-sentence enumeration of possible agent types ('a person, brand, product, business, character, coach or specialist') is mildly redundant padding but does convey scope breadth.

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?

With three parameters, no output schema and no nested objects, the description covers what an agent most needs: required inputs, that a link is returned instead of an agent, and that nothing persists. It stops short of saying what happens on handle collision or what the link looks like, which would be the remaining gaps.

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 description coverage is 100%, so the meaning of name, handle and description is already fully documented, including the derived-from-name fallback and the 5–15 character handle rule. The description only restates the intent at a high level and adds no format, constraint or edge-case detail beyond the schema.

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?

States a specific verb and resource ('Prepare a new public AI agent') plus the inputs it needs and what it returns, so an agent can tell this is a creation/drafting step rather than a conversational one. It never names a sibling such as find_agents or get_agent, so differentiation is inferred from verb choice rather than stated.

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?

Usage is implied: call it when you have a name and a description for a would-be agent. The closing clause clarifies the boundary of the action ('Nothing is created or reserved until they do'), which is a useful scoping cue, but there is no explicit 'when not to use' or named alternative for checking whether an agent already exists.

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.

Resources