Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_pool_status

Read-only

Check your research pool membership, published versus private items, counts, and join or leave links before joining or leaving. Add report=true to see your graded fill report.

Instructions

Get this account's research pool status (the pool is mainnet only): joined or not (and when), what is published and what stays private, the pool's latest counts, the scoreboard URL and how to join or leave. report=true adds your own graded report from your public fills since joining: win rate, mean R with ranges, labelled fluke or edge (members only). Use before join_pool or leave_pool and to see your grade; not for market data or balances (get_account) or your fills (get_history). Reads local files (the report also reads your public fills); signs and publishes nothing. Returns the status object, or {status, report}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pool_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportNoAdd your own graded trade report (members only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true by disclosing side-effect boundaries ('signs and publishes nothing'), data provenance ('reads local files'; the report also reads your public fills), the mainnet-only constraint, member-only access for report, and the exact return shape. These are the operationally risky details an agent needs before calling.

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?

Front-loaded with the core purpose, then scope, then usage guidance, then return behavior — a sensible ordering. It is dense with parentheticals and semicolons, so it scans less cleanly than it could, but almost no clause is redundant.

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?

No output schema exists, and the description compensates by naming the return shape ('the status object, or {status, report}'). Combined with stated data sources and side effects, nothing an agent needs to invoke this correctly is missing.

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?

Schema coverage is 100%, so a 3 was the floor, but the description adds real meaning to the single flag: report=true yields win rate, mean R with ranges, and a fluke/edge label drawn from public fills since joining — plus a members-only caveat. That tells the agent what opting in actually costs and produces.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and scope: 'this account's research pool status (the pool is mainnet only)' and enumerates exactly what status comprises — membership, publication/privacy, counts, scoreboard URL, join/leave. It is immediately distinguishable from get_account, get_history, and the join_pool/leave_pool siblings.

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

Usage Guidelines5/5

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

Explicit routing both ways: 'Use before join_pool or leave_pool and to see your grade' for when to call, plus exclusions naming the correct alternatives ('not for market data or balances (get_account) or your fills (get_history)'). Very little is left to inference.

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