Skip to main content
Glama
Sign In

iDevice Buyer's Guide

by com.idevice
OverviewDiscussionsAdmin

A reporter's or outlet's track record

source_track_record
Read-onlyIdempotent

For one reporter or outlet, by name: its pre-release reports graded against what the company later announced (Right, Partly right, Wrong), how many are not graded yet, the share right or partly right over graded reports only, its most recent graded reports with their dates, and the reports iDevice credits it with being first to make. profile_url links its page on idevice.com when that page holds a reporting record.

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

Input Schema

NameRequiredDescriptionDefault
nameYesA reporter's or outlet's name, e.g. 'Mark Gurman' or 'The Information'

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?

With annotations already covering read-only, idempotent, non-destructive behavior, the description adds strong context about what data is returned: grading categories, ungraded counts, accuracy share, recent graded reports, and conditional profile_url inclusion. It does not explain error behavior or ambiguity handling, but the return behavior is well disclosed.

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 one dense but front-loaded sentence that lists the returned data without obvious filler. It could be slightly more scannable, but every clause appears to serve a purpose.

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?

There is no output schema, so the description must explain what the tool returns, and it does so comprehensively by naming the grading breakdown, ungraded count, accuracy share, recent reports, first-to-report credits, and profile_url condition. It lacks only edge-case or error-handling detail.

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%, and the single 'name' parameter is already documented with examples in the schema. The description reinforces that the name refers to one reporter or outlet, but adds little beyond what the schema provides.

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 clearly states it returns a reporter's or outlet's track record, including graded pre-release reports, ungraded counts, accuracy share, recent reports, first-to-report credits, and profile URL. The resource and scope are specific, though it does not explicitly distinguish itself from siblings like get_reports or get_company_profile.

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 phrase 'For one reporter or outlet, by name' implies the tool is used to look up a source's track record, but there is no explicit when-to-use guidance, prerequisites, or naming of alternatives. The intended usage is clear enough but left implicit.

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

All iDevice Buyer's Guide 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