userUser profile(s) by handle (up to 10000 semicolon-separated).
| Name | Required | Description | Default |
|---|---|---|---|
| handles | Yes | 1-10000 handles |
| Name | Required | Description | Default |
|---|---|---|---|
| result | No | Array of user profile objects | |
| status | Yes | Response status (OK or FAILED) | |
| comment | No | Error comment (if status is FAILED) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds the 'up to 10000' limit but no further behavioral context (e.g., data freshness, rate limits).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely short, but 'profile(s)' is awkward and the semicolon mention is misleading. Could be clearer without increasing length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given output schema exists, basic completeness is achieved. However, lacks information on case sensitivity, profile fields returned, and relationship to sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% but the description mentions 'semicolon-separated' while the schema uses an array, creating ambiguity. Does not clarify whether the API expects a string or array.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves user profiles by handle, and specifies the batch capability (up to 10000). It distinguishes from sibling tools by mentioning handles and semicolon separation, but could be more precise.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'entity_profile' or 'user_rating'. Missing context for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set mixes Codeforces-specific tools with a large Pipeworx data toolkit. Within the Pipeworx family, ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical (the beta explicitly matches the stable version today), and deep_research/discover_tools/suggest_questions also overlap as meta entry points, creating real selection hazard. An agent could easily misselect among these.
Naming patterns are mixed: some tools use verb_noun (list_subscriptions, validate_claim, resolve_entity), some use bare verbs (remember, forget, recall), and some are noun phrases (problemset, blog_entry_view, recent_actions). Word order also varies (contest_list vs list_subscriptions), so no consistent convention is followed.
39 tools is far too many for a server named 'Codeforces' — only 8 tools actually concern Codeforces, while the remaining 31 are unrelated Pipeworx/utility tools. This bloats the surface and makes the server feel unfocused, especially for an agent expecting a compact Codeforces API.
For the Codeforces domain, the core read-only API is covered (contests, standings, problems, user info/rating/status, blog entries, recent actions) but some endpoints are missing (blog comments, rated list, problem statements). The large number of extra tools does not fill these gaps and instead obscures the intended purpose.