Skip to main content
Glama

What moved this week

what_moved_this_week
Read-only

The numbers whose value changed in the last seven days: funding rounds, valuations and prices first, then the biggest moves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "what_moved_this_week"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish read-only, closed-world behavior, so the description's added value is the prioritization rule ('funding rounds, valuations and prices first, then the biggest moves'). It does not say how 'biggest' is measured, how many items are returned, or whether the window is rolling or calendar-aligned.

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?

A single sentence with no filler, and the time window plus the category ordering are front-loaded. The phrasing 'The numbers whose value changed' is slightly roundabout but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description is the main source of return-value expectations, and it only partially delivers: it implies an ordered list but not its size, shape, or how ties/'biggest' are determined. Adequate to select the tool, thin for predicting what comes back.

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?

The tool takes zero parameters, which is the baseline-4 case; nothing in the schema needs explaining. The description sensibly uses its space on scope and ordering instead of inventing parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description narrows the resource to 'numbers whose value changed in the last seven days' and lists domains (funding rounds, valuations, prices), which goes beyond the title. But it is a noun phrase with no verb and no explicit statement of what the tool does with them (list? rank? summarize?), leaving the core action implicit.

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

Usage Guidelines2/5

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

No when-to-use guidance and no mention of alternatives such as get_history or search_numbers. An agent must infer that this is a weekly digest rather than a filtered query, with no stated exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.