Skip to main content
Glama
richer-richard

arquimedes-mcp

by richer-richard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

arquimedes_get_problem

Read-onlyIdempotent

Fetch a competition math problem by id to get its LaTeX statement, answer choices, answer, difficulty, source, and solutions with hints. Discover ids with search or sample first.

Instructions

Fetch one problem by its id, as returned by arquimedes_search_problems or arquimedes_sample_problems (e.g. 'prob.ahsme-1950-p10', 'prob.numina-000369'). Returns the full record: LaTeX statement, answer choices, answer, written solutions with progressive hints, difficulty, source, and diagram references. Ids cannot be guessed; an unknown id returns an error, so discover ids with search or sample first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
problem_idYesProblem id from a search or sample result (e.g. 'prob.ahsme-1950-p10', 'prob.aops-000000').
include_tracesNoAlso include the three long model-reasoning traces stored with deepmath problems (default false; each trace is typically over 10,000 characters).
include_solutionsNoInclude written solutions and their hints (default true). Set false to quiz without spoilers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • changedInput schema / properties / include_solutions / description
      Previous value: -"Include written solutions and hints (default true)."New value: +"Include written solutions and their hints (default true). Set false to quiz without spoilers."
    • changedInput schema / properties / include_traces / description
      Previous value: -"Include long-CoT R1 reasoning traces for deepmath records."New value: +"Also include the three long model-reasoning traces stored with deepmath problems (default false; each trace is typically over 10,000 characters)."
    • changedInput schema / properties / problem_id / description
      Previous value: -"Unique problem identifier (e.g. 'prob.ahsme-1950-p10', 'prob.aops-000000')."New value: +"Problem id from a search or sample result (e.g. 'prob.ahsme-1950-p10', 'prob.aops-000000')."
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the id-discovery requirement and the error behavior on unknown ids, plus a preview of what the record contains. It stops short of describing trace/solution cost implications beyond the schema, but this is solid added context.

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?

Three sentences, front-loaded with the action and then the prerequisites and return shape. No filler; every clause carries information the agent needs.

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?

With no output schema, the description usefully enumerates the returned record (statement, choices, answer, solutions with hints, difficulty, source, diagrams). Combined with the id-discovery guidance and annotations, an agent has everything needed to call this correctly.

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 coverage is 100%, so all three parameters are already documented in the schema, including the include_traces size warning and the include_solutions spoiler note. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

Specific verb+resource ('Fetch one problem by its id') with the id format exemplified ('prob.ahsme-1950-p10'). It clearly separates this single-record fetch from the sibling list tools arquimedes_search_problems and arquimedes_sample_problems.

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?

Explicitly states that ids cannot be guessed and that discovery must happen through search or sample first, naming both sibling tools as the route. It also gives the failure condition ('an unknown id returns an error'), which tells the agent when this call will not work.

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