Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_public_data

Retrieve Polymarket fee type reference data as rows, optionally filtered by active status or search term. Returns fetched_at timestamps for checking fee type details.

Instructions

Polymarket fee types. Returns Polymarket's fee type reference data as rows under data, optionally narrowed with active (true or false) or a search term. The response includes a fetched_at time. An invalid active value returns an invalid-parameter error.

Input Schema

NameRequiredDescriptionDefault
activeNoOptional upstream active filter
searchNoOptional upstream search filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / active / enum
      Added value: +[
+  "true",
+  "false"
+]
  2. Addedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavior: results come back as rows under `data`, a `fetched_at` timestamp is included, and an invalid `active` value yields an invalid-parameter error. It omits anything about auth, rate limits, or whether the reference data is static, so the disclosure is partial.

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?

Three tight sentences with no padding, and the resource ('Polymarket fee types') is front-loaded ahead of the filter and response details. The opening fragment is terse but functional rather than wasteful.

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 describe return values, and it does: rows under `data` plus a `fetched_at` field, and error behavior for bad input. For a zero-required-parameter reference-data tool this is nearly complete, with only auth/rate-limit context 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%, so the schema already documents both parameters. The description restates the `active` true/false values and characterizes both as narrowing filters, adding only marginal meaning beyond the schema. Baseline 3 applies.

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: it returns Polymarket's fee type reference data. That is far more specific than the vague tool name 'polymarket_public_data' implies. It stops short of distinguishing itself from anything else, but no sibling tool covers fee types, so there is little to differentiate from.

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?

Usage is only implied: the agent learns the result can optionally be narrowed by `active` or a `search` term, which suggests when to pass filters. There is no explicit statement of when to call this versus an alternative, and no exclusions or prerequisites. Adequate but thin.

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

Deploy Server

Other Tools