Skip to main content
Glama

Search Monity Network

search_network

Search the public Monity Network by keywords or page address to find published trackers and their creators, including slugs for use with other Network tools.

Instructions

Search the public Monity Network: trackers people publish on pages they track (prices, stock, releases, pricing pages, status pages, policies), and the people who run them. Give words ("ps5 restock", "openai pricing") or a page address. Returns trackers and people with their slugs for the other Network tools. In the results, watches are trackers with one source, watchlists are trackers with several, and hunters are people.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly one kind (default all): watches and watchlists are trackers, hunters are people
limitNoResults per kind (default 20)
queryYesWords, or a page address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does reasonably well: it discloses that results are public, that they include both trackers and people, that each carries a slug for downstream tools, and it defines the three result categories (watches = one source, watchlists = several, hunters = people). It omits ordering/relevance behavior, whether matching is fuzzy or exact, and any rate or auth notes beyond the word 'public'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what is searched, then what input to give, then what comes back and how to interpret it. The inline examples ('ps5 restock', 'openai pricing') and the watches/watchlists/hunters gloss each earn their place; nothing is padded or repeated.

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?

For a 3-parameter read-only search with full schema coverage and no output schema, the description covers the essentials: scope, accepted input forms, return contents, result taxonomy, and the downstream handoff via slugs. Gaps are minor — no mention of result ordering, pagination beyond the schema's limit, or what an empty result implies.

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 3 is the baseline, but the description adds real meaning beyond it: the schema only says 'watches and watchlists are trackers, hunters are people', while the description explains the distinction as one source versus several sources, which directly informs how to set the `type` filter. The 'words or a page address' guidance largely restates the schema, and `limit` gets no commentary, keeping it below a 5.

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 the public Monity Network') and enumerates exactly what is searched: trackers on pages people track (prices, stock, releases, policies) plus the people running them. This clearly positions it as the discovery entry point that produces slugs for the other Network tools, so an agent can distinguish it from get_network_watch/get_network_product 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 Guidelines3/5

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

Usage is implied rather than stated: 'Give words ... or a page address' plus the note that results carry slugs 'for the other Network tools' tells the agent this is the lookup-first step before get_network_* calls. However, there is no explicit when-not guidance and no named alternative (e.g. find_existing_network_watch or ask_network), so routing between search and those siblings is left to inference.

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