Skip to main content
Glama

Frantic

by com.gofrantic
OverviewDiscussionsAdmin

Get Frantic posting status

frantic.get_posting
Read-onlyIdempotent

Read a private vendor posting intake status through GET /v1/vendor-postings/{intake_id}. Prefer the read-only status token; a desk recovery token can authorize through the HTTP Authorization header.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intake_idYesVendor intake id returned by frantic.post_bounty.
status_tokenNoRead-only private status token returned by frantic.post_bounty.
operator_tokenNoPoster desk recovery token, used as desk authorization when no status token is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / operator_token / description
      Previous value: -"Poster operator token, used as desk authorization when no status token is available."New value: +"Poster desk recovery token, used as desk authorization when no status token is available."
  2. Changed4 schema fields changed
    • changedInput schema / properties / operator_token / description
      Previous value: -"Poster operator token."New value: +"Poster operator token, used as desk authorization when no status token is available."
    • removedInput schema / properties / operator_token / minLength
      Removed value: -1
    • addedInput schema / properties / status_token
      Added value: +{
+  "description": "Read-only private status token returned by frantic.post_bounty.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "intake_id",
-  "operator_token"
-]New value: +[
+  "intake_id"
+]
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/openWorld, so the description's added value is the disclosure that this is a private resource and how authorization works — status token preferred, desk recovery token as fallback via the HTTP Authorization header. That is real behavioral context beyond the structured fields.

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 sentences, zero filler, and the resource/endpoint is front-loaded before the auth caveat. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a status-reading tool with no output schema, the description says nothing about what the returned status actually contains or its possible states. It covers purpose and auth adequately but leaves the return-value gap unaddressed, making it only minimal-to-adequate for a tool whose whole job is reporting status.

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%, so the baseline is 3, but the description adds the preference ordering between status_token and operator_token and the transport detail (HTTP Authorization header) that the schema does not spell out. It still omits anything beyond the schema for intake_id, so it is not a 5.

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?

Specific verb (Read) and resource (private vendor posting intake status) plus the exact endpoint GET /v1/vendor-postings/{intake_id}. It does not explicitly distinguish itself from close siblings like frantic.get_bounty or frantic.get_claim, so it falls short of 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?

Gives auth-selection guidance ('Prefer the read-only status token; a desk recovery token can authorize'), which is useful context, but never states when to call this tool versus the sibling read tools that also surface bounty/claim state. Usage is implied rather than contrasted against alternatives.

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

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