Cronometer MCP

search_activities

Read-onlyIdempotent

Find Cronometer exercise activities by name to obtain IDs for adding exercise to your diary. Query words must match the activity name; returns up to 50 IDs.

Instructions

Search Cronometer's exercise activities by name, for add_exercise.

Every word of the query must appear in the name, e.g. "running 6 mph" or "cycling". Returns up to 50 activity ids.

Args: query: Words to look for in the activity name.

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": {
      "query": "<query>"
    },
    "name": "search_activities"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Nov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the AND-matching rule ("every word of the query must appear in the name") and a result cap of 50 activity ids. It does not explain what happens when zero matches occur, which keeps it from a 5.

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?

Purpose is front-loaded in one line, followed by the matching rule and the return limit, then a short Args block. The Args entry largely restates the first sentence's "by name", a small redundancy, but nothing else is wasted.

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?

With an output schema present, the description need not document the return shape, yet it still discloses the 50-id cap. For a single-parameter read-only search this is close to complete; only edge-case behavior (no matches, case handling) is left unspecified.

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 description coverage is 0%, so the description must carry the query parameter, and it does: "Words to look for in the activity name" plus the conjunctive matching rule. The two worked examples ("running 6 mph", "cycling") clarify token-level rather than substring matching. Minor gap: no note on case sensitivity or empty-query behavior.

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?

States a specific verb and resource ("Search Cronometer's exercise activities by name") and immediately scopes it to a downstream consumer ("for add_exercise"). This clearly separates it from search_foods, the other lookup sibling, without needing to open either schema.

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?

"for add_exercise" tells the agent exactly which workflow this feeds and that it is a lookup step preceding a write. It does not explicitly state when not to use it or name an alternative for non-exercise lookups, so it falls short of full when/when-not guidance.

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

Deploy Server