Skip to main content
Glama

Attify

Traction reports and share links

list_traction_reports
Read-onlyIdempotent

Your company's audited traction reports: status, summary, the months and customers covered; for one report, its share links (who each is for, state, expiry, email allowlist, views) and who opened it, from the view log. A link's address is shown once when it is made and never stored, so it cannot be read back. Needs sign-in to Attify; reads only.

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

Input Schema

NameRequiredDescriptionDefault
reportNoOne report's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety profile is covered. The description still adds real value beyond them: the sign-in requirement and especially the warning that a share link's address is shown once and never stored, so it cannot be read back. It does not describe pagination or ordering for the list mode.

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?

One front-loaded sentence plus a short operational note; nothing is padding. The lead sentence is densely packed with semicolons and colons, which costs a little readability.

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 no output schema, the description carries the return-shape burden and does so well by enumerating the fields returned in both modes. Auth and the one-way link-address caveat cover the main behavioral risks for a read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one optional param, so the baseline is 3. The description earns an extra point by explaining what supplying it does: it switches the response to that one report's share links and view log rather than the report list.

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 names the resource (audited traction reports) and enumerates what is returned: status, summary, covered months and customers, plus share links with their state, expiry, allowlist, views and openers. That is concrete and far beyond a restatement of the name. It does not name or differentiate itself from the sibling get_traction_report, so an agent must infer why both exist.

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?

It states a precondition ("Needs sign-in to Attify; reads only") and implies two modes, all reports or a single report by id, but never says when to pick this over get_traction_report. Usage is inferable rather than guided.

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