Skip to main content
Glama

agentery

by com.agentery
OverviewDiscussionsAdmin

Find a market

find_market
Read-only

Use when someone asks what a kind of product typically costs or who competes in a space, e.g. 'what should I charge for lead-generation automation' or 'tools that monitor competitor pricing'. Maps the task to its market (the nearest providers by meaning, no fixed categories) and returns the market label, provider and priced counts, the nearest providers with observed prices, and pricing_by_tier (median, p25/p75, range and n per buyer tier). When nothing is close it returns no_match or thin_coverage and withholds pricing rather than invent a market. For market plus shortlist in one call use research_capability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesREQUIRED. A natural-language task, capability or service in plain words, e.g. 'reconcile supplier invoices'. Call as {"task": "…"}; an empty call returns status needs_input with an example and searches nothing.
queryNoAlias for task (back-compat only) — prefer task

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
-  {
-    "required": [
-      "task"
-    ]
-  },
-  {
-    "required": [
-      "query"
-    ]
-  }
-]
    • changedInput schema / properties / query / description
      Previous value: -"Alias for task (back-compat) — a natural-language task, capability or service"New value: +"Alias for task (back-compat only) — prefer task"
    • changedInput schema / properties / task / description
      Previous value: -"A natural-language task, capability or service, e.g. 'reconcile supplier invoices'"New value: +"REQUIRED. A natural-language task, capability or service in plain words, e.g. 'reconcile supplier invoices'. Call as {\"task\": \"…\"}; an empty call returns status needs_input with an example and searches nothing."
    • addedInput schema / required
      Added value: +[
+  "task"
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a safe, closed-world read, so the safety bar is low. The description goes further with a behavioral trait the annotations cannot express: it withholds pricing and returns no_match/thin_coverage rather than inventing a market. It also describes the return payload (label, counts, nearest providers, pricing_by_tier percentiles), which is real disclosure beyond the safety hints.

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 usage trigger, then payoff, then failure mode, then the alternative — a logical order with no filler sentences. It is dense and slightly list-like in the returns enumeration, but each clause carries distinct information an agent needs.

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?

No output schema exists, so the description correctly carries the burden of describing return values — and it does so in detail (market label, provider/priced counts, nearest providers with observed prices, pricing_by_tier medians/quartiles/range/n). Combined with the fallback behavior and the routing hint, nothing needed to call it correctly 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 description coverage is 100%, with both `task` and its alias `query` fully documented in the schema, including the empty-call behavior. The description adds only the 'no fixed categories' framing for how `task` is interpreted, which is marginal semantic value. Baseline 3 applies when the schema does the heavy lifting.

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 ('maps the task to its market') and immediately scopes it ('nearest providers by meaning, no fixed categories'). It also enumerates exactly what comes back, so the agent knows this is not a generic search tool. It differentiates from the closest sibling by naming research_capability and the condition that selects it.

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?

Opens with an explicit trigger ('Use when someone asks what a kind of product typically costs or who competes in a space') backed by two concrete example queries. It names the alternative tool and the exact situation that should route there ('market plus shortlist in one call'). Edge-case guidance (no_match / thin_coverage) covers the failure path as well.

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

All agentery toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources