Skip to main content
Glama
Sign In

PointRover

by com.pointrover
OverviewDiscussionsAdmin

Published Index Series

pointrover_series
Read-only

Returns the published index for one input the business buys or one wage it pays: the latest figure, its twelve-month move and how unusual that move is. Use this when the assistant is checking whether a supplier's increase is in line with the market. Not for the business's own books: invoices, bank, payroll or accounting live in its accounting connector, not here. Nor is it fetch: this is the history of one number, not the item around it. It also says whether a figure is preliminary or corrected and, where measured, the share of an upstream move reaching the business. Pass series_id (string, the publisher's own id, for example "PCU324191324191"), window (integer, trailing periods) and include_observations (boolean). Example: pointrover_series({"series_id": "PCU324191324191"}).

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": {
      "series_id": "<series_id>"
    },
    "name": "pointrover_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoHow many trailing published periods to consider. Defaults to the board's own display window, which is every period it carries for this series.
series_idYesThe publisher's own series id, as this board carries it.
include_observationsNoReturn each period's figure. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations only declare `readOnlyHint: true`, so the description usefully adds that the response includes the latest figure, the twelve-month move, unusualness, preliminary/corrected status, and upstream pass-through share where measured. It does not discuss error behavior, rate limits, or permissions, but it provides meaningful output context beyond the annotation.

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?

The description is front-loaded with purpose and scope, then usage exclusions, then output behavior, and finishes with parameter guidance and an example. It is somewhat dense and repeats parameter names already documented in the schema, but most sentences earn their place by distinguishing siblings or clarifying scope.

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?

For a read-only tool with three documented parameters and no output schema, the description is complete enough: it explains what is returned, when to use it, when not to use it, and how it differs from siblings. The remaining parameter syntax is handled by the schema, so no critical context is missing.

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 the schema already defines all three parameters, including the window default and boolean semantics. The description adds a concrete `series_id` example (`PCU324191324191`) and an example call, but otherwise mostly restates parameter names rather than adding substantial new meaning beyond the 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 states a specific verb and resource: it returns the published index for a purchased input or paid wage, including the latest figure, twelve-month move, and unusualness. It also distinguishes this history-of-one-number tool from `fetch`, which handles the item around the number, so an agent can select it confidently.

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?

It gives an explicit use case: checking whether a supplier's increase is in line with the market. It also states when not to use it, naming the accounting connector for invoices, bank, payroll, and accounting, and explicitly contrasts it with `fetch`. This covers when, when-not, and alternatives.

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

All PointRover toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources