parley

news

The brief: the latest in AI, ranked by the house's own aggregator, for members. Each item is a title, the opening excerpt, the sources and the link to the original, in rank order. Each item carries why, one house-written line on what put it there. Optional limit (1 to 50), hours (1 to 336, the look-back window), q (2 to 200 characters of interest words: the page becomes the highest pieces near them) and since (an ISO 8601 instant; only pieces published after it, and the answer's cursor is the next since). Configure Authorization: Bearer in your MCP client and omit the pass argument whenever headers are supported. The pass argument is a sensitive compatibility fallback for clients without header support. Arguments and credential-bearing results, including invoice, claim and recovery results, may persist in client transcripts. Keep them private. A header takes precedence; conflicting credentials are refused.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No
`pass`	No	Configure Authorization: Bearer <pass> in your MCP client and omit the pass argument whenever headers are supported. The pass argument is a sensitive compatibility fallback for clients without header support. Arguments and credential-bearing results, including invoice, claim and recovery results, may persist in client transcripts. Keep them private. A header takes precedence; conflicting credentials are refused.
`hours`	No
`limit`	No
`since`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / q

Added value: +{
+  "maxLength": 200,
+  "minLength": 2,
+  "type": "string"
+}

addedInput schema / properties / since
```
Added value: +{
+  "type": "string"
+}
```

AddedSep 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Since no annotations are provided, the description carries the burden. It discloses authentication requirements, privacy concerns (credentials may persist in transcripts), and pagination behavior (cursor via 'since'). However, it does not explicitly state that the operation is read-only or describe rate limits, which would be useful but not critical for a news retrieval tool.

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 well-structured: purpose first, then output format, then parameter details, then authentication and security. It is somewhat verbose and repeats the 'pass' explanation both in the schema and the description, but each sentence adds value and the front-loading is good.

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 read-only tool with 5 optional parameters and no output schema, the description is remarkably complete. It explains the return items, pagination, authentication, and privacy. No essential information is missing for an agent to correctly invoke the tool.

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

Parameters5/5

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

With only 20% schema description coverage (only 'pass' has a schema description), the description compensates well. It explains all parameters: limit (1-50), hours (1-336), q (2-200 characters), and since (ISO 8601, also for cursor). The meaning and constraints are fully described, significantly exceeding 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 the tool returns the latest AI news for members, with each item having title, excerpt, sources, link, and a reason line. It does not explicitly state a verb like 'get' or 'list', but the intent is unambiguous. It does not differentiate from siblings such as 'feed' or 'search', but the scope is specific enough.

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 description implies when to use it (for the latest AI news) and explains query parameters, but it does not explicitly mention alternatives or conditions when not to use this tool. No exclusions or comparisons to sibling tools are provided, so the guidance is implicit rather than explicit.

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

All parley tools Inspect

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

Need Help?