Skip to main content
Glama

Attify

Read a shared traction report

get_traction_report
Read-onlyIdempotent

A company's audited traction report, from a share link it gave you: the summary and auditor-style opinion, up to three key numbers, each claim tested (supported, not supported, not testable), then usage, retention, pilot to production, concentration and outcome rates per customer-month, every number with its sample size, period, evidence tier and provenance (connected, or witnessed data the customer reconciled; never uploads), and the signed attestation. Opening it is logged in the company's view log. Links limited to named people need a browser sign-in.

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

Input Schema

NameRequiredDescriptionDefault
tokenNoThe token at the end of the share link.
share_urlNoThe share link, e.g. "https://…/r/AbC…".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses a real side effect (opening the report is logged in the company's view log) and an auth requirement for restricted links. It also bounds the data: provenance is connected or witnessed-reconciled data and never uploads, which is behavioral context the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a single dense run-on sentence that chains the entire report inventory together. Much of that enumeration is useful content, yet the structure makes it hard to scan and could be broken into distinct sentences.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: summary, auditor-style opinion, per-claim test results, usage/retention/concentration/outcome rates, and evidence tier and provenance on every number. For a read-only tool with only two parameters, nothing essential to calling it correctly is missing.

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%, with both token and share_url documented in the schema itself, so the baseline applies. The description mentions the share link but does not clarify the relationship between the two parameters — for example whether token is derived from share_url or which one takes precedence.

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 states a specific resource (a company's audited traction report) and its access path (a share link the company gave you), which lets an agent separate it from the list-style siblings. It stops short of naming a sibling such as list_traction_reports, so the differentiation is inferred rather than explicit.

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?

It gives a clear selection condition — use this when the company has handed you a share link — and states a prerequisite that links limited to named people require a browser sign-in. There is no explicit when-not guidance or named alternative for the case where no share link 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