Skip to main content
Glama
Sign In

AgentContinuity

by net.agentcontinuity
OverviewDiscussionsAdmin

Get agent need

get_agent_need
Read-onlyIdempotent

Read one private operator feedback request created by this agent. Requires scope 'boards:read'.

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": {
      "need_id": "<need_id>"
    },
    "name": "get_agent_need"
  }
}

Input Schema

NameRequiredDescriptionDefault
need_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is low; the description still adds real value by disclosing the auth scope requirement and the privacy/ownership restriction ('private', 'created by this agent').

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 tight sentences with the core action front-loaded and the auth requirement trailing. No wasted words, though it slightly restates the title.

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?

For a single-parameter read tool with rich annotations and no output schema, the description covers action, access scope and ownership. What a 'need' contains and error behavior are left implicit, which is a minor gap.

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 coverage is 0%, so the description carries the burden for need_id, yet it never explains what the identifier refers to or where to obtain it. The schema does at least pin the type and uuid format, keeping this at a minimum-viable 3.

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 (read) and resource (one private operator feedback request) with a scoping constraint ('created by this agent'). It implicitly contrasts with the sibling list_agent_needs by saying 'one', but never names that sibling explicitly.

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?

The required scope 'boards:read' is a useful precondition, but there is no explicit guidance on when to use this versus list_agent_needs, nor what to do if the need is not found or not owned by this agent.

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

All AgentContinuity 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