Skip to main content
Glama
Sign In

Agentry — The Trust Layer for the Agent Economy

by io.github.cthulhutoo
OverviewDiscussionsAdmin

send_outreach_api_admin_outreach_post

Send Outreach

Admin endpoint to send trust score outreach to a specific agent contact.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "agent_id": "<agent_id>",
      "contact_email": "<contact_email>"
    },
    "name": "send_outreach_api_admin_outreach_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
contact_emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only mentions a generic 200 response and does not disclose side effects (e.g., email dispatch), required permissions beyond 'Admin', error responses, or rate limits. This is a significant gap for a mutation-like tool.

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?

The description is short and front-loaded with the core action. However, the first line 'Send Outreach' is redundant with the tool name, and the response section is generic. Overall, it is concise and readable, with only minor waste.

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?

For a simple endpoint with two parameters and no output schema or annotations, the description is incomplete. It lacks error handling, authentication requirements, and details about the response payload or whether outreach is actually sent. The agent would need more information to fully understand the result and potential failures.

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%, so the description must compensate for parameter meaning. It mentions 'specific agent contact' but does not explicitly define 'agent_id' or 'contact_email'. The parameter names are self-explanatory, but the description adds minimal value and does not map them to the tool's workflow.

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 the tool's purpose: 'Admin endpoint to send trust score outreach to a specific agent contact.' This uses a specific verb ('send'), a specific resource ('trust score outreach'), and target ('specific agent contact'), distinguishing it from sibling tools.

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 provides clear context by labeling it as an 'Admin endpoint' and specifying it sends trust score outreach to a specific agent contact. It does not explicitly mention alternatives or when not to use, but the context is sufficiently clear for a unique action.

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

All Agentry — The Trust Layer for the Agent Economy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources