Skip to main content
Glama

Check a 360's progress

check_360_status
Read-only

Check the progress of the user's own 360 from the private link in their 360 email (…/campaigns/access/…): self-assessment done, number of reviewer answers, deadline, whether the report is ready. Returns counts only, never names, emails or feedback.

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": {
      "private_link": "<private_link>"
    },
    "name": "check_360_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
private_linkYesThe private link from the 360 email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context — the result is aggregate counts only, never names, emails or feedback — which tells the agent what data is and isn't exposed. It does not cover what happens with an expired or invalid link, which is the main behavioral gap.

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 compact sentences, front-loaded with the action and then the output/privacy constraint; nothing is padded. The parenthetical path fragment is slightly cryptic but earns its place by identifying the expected input.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with no output schema, the description covers purpose, required input provenance, and the shape of the returned data (counts, deadline, report readiness). An agent has everything needed to decide to call it and interpret the response.

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?

With a single parameter at 100% schema coverage, the schema already documents private_link fully. The description adds modest value by showing the link's shape ('…/campaigns/access/…'), helping the agent recognize a valid input, but it adds no length or format constraints beyond that.

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?

States a specific verb and resource ('Check the progress of the user's own 360') plus the exact scope ('from the private link in their 360 email') and enumerates what is reported (self-assessment done, reviewer answer counts, deadline, report readiness). 'Own 360' and the private-link framing clearly separate it from start_360 or comparison 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?

Gives clear context for when it applies: the caller must hold the private link from the 360 email, which implies this is a participant-facing progress check rather than an admin view. It stops short of naming an alternative for admins or for the 360 owner who lacks the link, so no explicit exclusion is stated.

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