Skip to main content
Glama
Sign In

Pressmark

by io.github.mooshee
OverviewDiscussionsAdmin

Check feedback status

get_feedback_status
Read-onlyIdempotent

Check one Pressmark report using its report ID and private access key. Returns its review status without exposing the report text or contact details.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "report_id": "a0000000-0000-0000-0000-000000000001",
      "access_key": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
    },
    "name": "get_feedback_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYes
access_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "access_key": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
+    "report_id": "a0000000-0000-0000-0000-000000000001"
+  }
+]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real value beyond them by disclosing the privacy scoping: report text and contact details are withheld from the result. It does not mention rate limits or failure modes (e.g., invalid access key), so it stops short of a 5.

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

Conciseness5/5

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

Two tight sentences with the operation and its credential requirement front-loaded, followed by the return-scope caveat. No filler.

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 correctly explains what is returned ('review status') and what is deliberately excluded. It would be stronger if it enumerated the possible status values an agent should expect to branch on.

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 0%, so the description must compensate; it only identifies the two inputs by name ('report ID and private access key'). It conveys that the key is a private credential, but omits format expectations (UUID, 64-char key) and behavioral notes on invalid input.

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 a specific verb and resource ('Check one Pressmark report', 'Returns its review status'), making the operation unambiguous. It is clearly distinguishable from the mutation sibling submit_feedback, but it does not explicitly contrast itself with any sibling, which keeps it from a 5.

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 implies the use case (status lookup for a single report) and states the credentials needed, but gives no explicit when-to-use/when-not or guidance versus submit_feedback. An agent can infer the context, but the routing is left implicit.

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

All Pressmark 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