Skip to main content
Glama
Sign In

get4agent

by com.get4agent
OverviewDiscussionsAdmin

Search the marketplace

search_listings
Read-onlyIdempotent

Search get4agent's catalog of services and data APIs from Regent-verified sellers, newest first. Each result has a price, the seller, the date it was added and a url to buy on get4agent.com. Results are paged: has_more and next_offset tell whether more results exist and where the next page starts. Public, no sign-in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNolisting kind: good | service | api | tool
limitNoresults per page, 1 to 50 (default 20)
queryNokeyword matched against title and description, e.g. "courier"
offsetNonumber of results to skip, e.g. 20 for the second page of 20 (default 0)
categoryNocategory slug, e.g. "financial-data" (case-insensitive)
verified_onlyNoonly sellers whose identity Regent verified (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"category slug from list_categories, e.g. \"financial-data\" (case-insensitive)"New value: +"category slug, e.g. \"financial-data\" (case-insensitive)"
    • changedInput schema / properties / offset / description
      Previous value: -"how many results to skip: next_offset from the previous page (default 0)"New value: +"number of results to skip, e.g. 20 for the second page of 20 (default 0)"
  2. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"category slug as listed, e.g. \"delivery\" (case-insensitive)"New value: +"category slug from list_categories, e.g. \"financial-data\" (case-insensitive)"
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "results per page, 1 to 50 (default 20)",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "how many results to skip: next_offset from the previous page (default 0)",
+  "minimum": 0,
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / verified_only / description
      Previous value: -"only KYA-verified sellers (default true)"New value: +"only sellers whose identity Regent verified (default true)"
  4. Changed5 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"category slug as listed, e.g. \"delivery\" (case-insensitive)"
    • changedInput schema / properties / kind / description
      Previous value: -"good | service | api | tool"New value: +"listing kind: good | service | api | tool"
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "good",
+  "service",
+  "api",
+  "tool"
+]
    • changedInput schema / properties / query / description
      Previous value: -"keyword (title/description)"New value: +"keyword matched against title and description, e.g. \"courier\""
    • changedInput schema / properties / verified_only / description
      Previous value: -"default true"New value: +"only KYA-verified sellers (default true)"
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: newest-first ordering, the fields each result contains (price, seller, date, buy url), and explicit pagination semantics via has_more and next_offset. With no output schema, this return-shape disclosure is exactly the value the description should provide.

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?

Four short sentences, front-loaded with purpose then result shape then paging then access. Every sentence carries distinct information and none repeats the schema.

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 six-parameter, all-optional search tool with no output schema, the description covers what is searched, ordering, result fields, pagination contract and auth requirements. Nothing an agent needs to call it correctly or interpret the response 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%, so every one of the six parameters is already documented with enums, defaults and bounds. The description adds no input-side detail (e.g. how query and category combine, or that verified_only defaults to true) beyond restating the verification concept, so the baseline 3 applies.

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 get4agent's catalog of services and data APIs'), plus scope qualifiers (Regent-verified sellers, newest-first ordering). This is clearly distinguishable from siblings like get_listing (single item) and list_categories (taxonomy), so an agent can choose without opening the 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?

Provides an access prerequisite ('Public, no sign-in') and implies a discovery use case, but never states when to use this instead of get_listing or list_categories. Usage is inferred from the verb rather than spelled out.

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

All get4agent 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