mcp-server-worldquantbrain

by tukorama

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Get my activity

get_user_activity

Read-onlyIdempotent

Retrieve simulation or submission counts for yesterday, month to date, year to date, and total activity.

Instructions

Return simulation or submission counts: yesterday, month to date, year to date, total.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "get_user_activity"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes	Activity type.

Output Schema

Name	Required	Description	Default
`ytd`	No
`kind`	Yes
`total`	No
`recent`	No
`current`	No
`previous`	No
`yesterday`	No
`total_rows`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's added value is the set of time buckets returned, which tells the agent what granularity to expect. It does not clarify the scope of 'my' (authenticated user vs. session), whether windows are calendar or rolling, or any timezone assumption, and it does not reconcile the openWorld flag with what appears to be a user-scoped read.

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?

One sentence, front-loaded with the verb and resource, with the output buckets enumerated compactly after the colon. No filler, no repetition, and it scales correctly for a single-parameter read tool.

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 spelled out, and the single required parameter is fully documented in the schema. What remains is a small gap around user scoping and authentication expectations for a 'my activity' tool, but nothing an agent needs in order to invoke it correctly is 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% and the single parameter is an enum with a description, so the schema already carries the burden. The description's 'simulation or submission counts' maps the enum values onto the returned metric, which is minor added meaning beyond 'Activity type.' 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 gives a specific verb (Return) and a specific resource (simulation or submission counts) and enumerates the exact breakdowns (yesterday, MTD, YTD, total). It is immediately clear what the tool returns, though it does not explicitly distinguish itself from neighbors like get_user_profile that an agent might also consider for user-level data.

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: an agent infers 'use this when you need activity counts.' There is no explicit when-to-use statement, no mention of alternatives or related tools, and no prerequisites (such as needing to be authenticated as a user). The naming of the two count kinds is the only routing signal offered.

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