Skip to main content
Glama

Ask Monity Network

ask_network

Answers plain-language questions about website changes using public Monity Network change records, with numbered citations; if coverage is missing, it reports noCoverage and provides a requestUrl to ask for a tracker.

Instructions

Ask a question in plain words ("What changed on nike.com this week?", "Is the PS5 Pro back in stock anywhere?", "Which GPUs dropped in price this month?"). Answered only from public Monity Network change records, each claim numbered [n] to its record in citations (with its page, values, date and evidence link). If Network has no coverage it says so (noCoverage) and gives requestUrl to ask for a tracker; it never answers from general knowledge. Relay citations to the person.

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": {
      "question": "<question>"
    },
    "name": "ask_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: answers are grounded only in public change records, each claim is numbered [n] to a citation carrying page, values, date and evidence link, and the no-coverage path returns a structured noCoverage flag plus requestUrl. It also states the tool refuses to answer from general knowledge, which is an important behavioral boundary. Gaps remain around authentication, latency, and whether citations are always present.

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-loaded with the verb and resource, then examples, then the grounding guarantee, then the no-coverage fallback, then the relay instruction. Parenthetical examples add length but each clarifies a distinct valid question shape. No filler sentences.

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 single-parameter question-answering tool with no output schema, the description covers what goes in, how answers are grounded and cited, and what the caller receives on failure (noCoverage + requestUrl). It even tells the agent what to do with the result ('Relay citations to the person'), leaving no major operational gap.

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 0% for the single 'question' parameter, but the description compensates by characterizing it as a plain-language question and giving three worked examples that show expected phrasing, scope and time framing. It does not mention the 3–300 character bounds, but that is a minor omission given the examples do the interpretive work.

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

Purpose4/5

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

Names a specific verb and resource: 'Ask a question in plain words' answered from 'public Monity Network change records.' The three sample questions make the scope concrete (price drops, restocks, site changes). It does not explicitly contrast with sibling lookup tools like query_network_records or search_network, so an agent must infer that this is the natural-language layer rather than the raw-record layer.

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

Usage Guidelines3/5

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

The example questions imply usage ('this week', 'back in stock', 'dropped in price'), and the description states that on no coverage it returns noCoverage plus a requestUrl to ask for a tracker. However, there is no explicit instruction on when to prefer this over record-level siblings, and no exclusions beyond 'it never answers from general knowledge.'

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