Skip to main content
Glama

Codeforces

by io.github.pipeworx-io

Search Within a Source

search_within
Read-onlyIdempotent

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe document text to search inside (max ~200K chars).
limitNoMax passages to return (1-20, default 5).
queryYesNatural-language query — what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".

TDQS

A4.6/5.0
Behavior5/5

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

Adds significant detail beyond annotations: embedding model, window size, character cap with truncation flag. No contradiction with annotations.

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 key purpose, but slightly long. All sentences earn their place except minor redundancy.

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?

Covers usage, behavior, limitations, and output format despite no output schema. Addresses all needed context for a retrieval tool.

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

Parameters4/5

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

Schema coverage is 100% with descriptions. The description adds that passages carry offsets (output detail), compensating for missing output schema.

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?

The description uses a specific verb ('semantic search') and resource ('inside a fetched record'), and clearly distinguishes from sibling tools like ask_pipeworx_grounded.

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

Usage Guidelines4/5

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

Explicitly states when to use (record too big for prompt) and pairs with a sibling tool. Does not list when-not-to-use but context is clear.

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

All Codeforces toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

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 Consistency2/5

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.

Tool Count2/5

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.

Completeness3/5

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.

Resources