Skip to main content
Glama

Problee

by com.problee
OverviewDiscussionsAdmin

Read dated market research and AI analyst takes

problee_get_market_research
Read-onlyIdempotent

Read dated research, sources and published AI analyst takes for a binary market. Research, not advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesChecksummed or lowercase 20-byte EVM address (0x + 40 hex).
chainIdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / MarketResearch / properties / analystCount
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / $defs / MarketResearch / properties / analystsAverage
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. Changed1 schema field changed
    • addedOutput schema / $defs / MarketResearch / properties / analysts / items / properties / reason
      Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • removedOutput schema / $defs / MarketResearch / properties / analysts / items / properties / priceAtTake / multipleOf
      Removed value: -0.0001
    • removedOutput schema / $defs / MarketResearch / properties / analysts / items / properties / probability / multipleOf
      Removed value: -0.0001
    • changedOutput schema / $defs / MarketResearch / properties / priceAtResearch / anyOf
      Previous value: -[
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "multipleOf": 0.0001,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
  4. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful content context (dated, sourced, AI-authored) and a 'not advice' disclaimer, but says nothing about volume, pagination, or freshness beyond 'dated'.

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 compact sentences with the resource and scope front-loaded and zero filler. Every clause earns its place.

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?

An output schema exists, so return values need not be described, and annotations cover the safety semantics. The description is nearly complete, lacking only differentiation from sibling retrieval tools and clarification of the undocumented chainId parameter.

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

Parameters2/5

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

Schema coverage is only 50%: 'address' is documented, but 'chainId' carries no schema description. The description adds no meaning for either parameter and never explains how chainId interacts with the market lookup, so it fails to compensate for the coverage gap.

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?

States a specific verb+resource: reading 'dated research, sources and published AI analyst takes' for a binary market. It clearly signals a research-retrieval tool, but does not explicitly differentiate itself from the close sibling problee_get_market_news or explain what 'AI analyst takes' contains versus news.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives situational context ('for a binary market' and 'Research, not advice') but offers no when-to-use versus alternatives, no prerequisites, and no pointer to sibling tools like problee_get_market_news. The agent must infer when this is the right call.

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

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