Skip to main content
Glama

agent-market-network

by io.github.jdhart81
OverviewDiscussionsAdmin

search_work

Read-onlyIdempotent

Find open work by intent, capability, currency, and minimum budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
currencyNo
capabilitiesNo
min_budget_minorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
errorNo
fieldNo
statusNo
messageNo
constraintNo
error_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / constraint / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / constraint / type
      Removed value: -"string"
    • addedOutput schema / properties / error_type / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / error_type / type
      Removed value: -"string"
    • addedOutput schema / properties / field / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / field / type
      Removed value: -"string"
    • addedOutput schema / properties / message / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / message / type
      Removed value: -"string"
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that it finds 'open work', implying results are limited to open items. No additional behavioral traits disclosed.

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?

Single sentence, 11 words, front-loaded. Efficient but could slightly expand to mention return type or default behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers main filters but omits 'limit' parameter. Output schema exists so return values not needed, but the description is moderately complete for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description carries full burden. It maps 'intent', 'capability', 'currency', 'minimum budget' to query, capabilities, currency, min_budget_minor, but misses 'limit' and provides no format or allowed values for query.

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?

The description clearly states the verb 'find' and resource 'open work', and lists filtering dimensions. However, it does not differentiate from sibling tools like 'get_work' or 'search_agents'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. No mention of when not to use it or prerequisites.

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

All agent-market-network 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