Skip to main content
Glama
Sign In

PointRover

by com.pointrover
OverviewDiscussionsAdmin

Search the Board

search
Read-only

Returns the inputs and their published indexes, tariffs, wages, locations, rules and events PointRover holds for the business that match a few words, each with an id and title. Use this when the assistant is looking up one material, a duty such as "section 232", or a job title. Not for the business's own books: invoices, bank, payroll or accounting live in its accounting connector, not here. Nor is it fetch, which opens one item by its id. Pass query (string; an id returns that item), limit (integer 1 to 25, default 10) and scope (business, the default; industry for the trade's typical products and inputs; all). Example: search({"query": "motor oil", "limit": 5}). Ranked by match, with no model.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return. Default 10, capped at 25.
queryYesWords to match against record names and their own words.
scopeNobusiness (the default): this business's own records. industry: the trade's typical products and inputs. all: both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

readOnlyHint=true already declares the safety profile, and the description adds real context on top: results are ranked by match with no model involved, and each row carries an id and title. It stops short of covering anything about paging beyond the limit cap or empty-result behavior, which is why it is a 4 rather than 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?

Front-loads the resource definition, then exclusions, then parameters and an example — a sensible order with no filler sentences. It is dense and slightly long for a search tool, but each clause (including the fetch exclusion and the example) carries routing or calling value.

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 supplies the return shape (id and title per row) and the ordering rule (ranked by match, no model), and it covers all three parameters including defaults and enum meanings. An agent has everything needed to decide to call it and to construct a correct call.

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%, so the baseline is 3, but the description goes further: it discloses that passing an id as query returns that specific item, and it restates scope values with practical framing (industry = the trade's typical products and inputs) plus a worked example call. That adds usable meaning beyond the schema's own wording.

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 (returns) plus the exact resource set: inputs, indexes, tariffs, wages, locations, rules and events matching a few words, each with id and title. It also draws the boundary against a named sibling ("Nor is it fetch, which opens one item by its id"), so an agent can separate the two without opening a schema.

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?

Gives concrete when-to-use triggers (looking up one material, a duty such as "section 232", or a job title) and explicit when-not-to-use cases (invoices, bank, payroll, accounting belong to the accounting connector; single-item retrieval belongs to fetch). Both the positive and negative routing conditions are stated rather than implied.

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