Skip to main content
Glama
Sign In

get4agent

by com.get4agent
OverviewDiscussionsAdmin

Get one listing

get_listing
Read-onlyIdempotent

Get one listing as schema.org Product JSON-LD: description, price, seller, the seller's verification status and the url to buy on get4agent.com.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYeslisting UUID, e.g. 3f9a8c1b-7d2e-4c5a-9b1f-2e8d4a6c0b17

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / listing_id / description
      Previous value: -"listing UUID from search_listings, e.g. 3f9a8c1b-7d2e-4c5a-9b1f-2e8d4a6c0b17"New value: +"listing UUID, e.g. 3f9a8c1b-7d2e-4c5a-9b1f-2e8d4a6c0b17"
  2. Changed1 schema field changed
    • addedInput schema / properties / listing_id / description
      Added value: +"listing UUID from search_listings, e.g. 3f9a8c1b-7d2e-4c5a-9b1f-2e8d4a6c0b17"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by specifying the exact return shape (schema.org Product JSON-LD with description, price, seller, verification status, buy URL), which no output schema provides. It stops short of stating not-found/error behavior.

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?

One front-loaded sentence with the return content enumerated inline; every clause carries information and there is no filler.

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?

With no output schema, the description compensates well by listing the fields returned for a single-record read tool. Only the failure/empty case (invalid or missing listing_id) is left unaddressed, a minor gap for a read-only lookup.

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 coverage is 100% and the single listing_id parameter is documented with a UUID example, so the description adds nothing parameter-specific. Baseline 3 is appropriate when the schema carries all parameter meaning.

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?

States a specific verb and resource ("Get one listing") and enumerates the returned payload fields, so the agent knows exactly what it retrieves. It does not explicitly name search_listings as the way to obtain a listing_id, but the singular "one listing" contrasts clearly enough with the sibling search tool.

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 only implied: the tool obviously applies when you already have a listing_id, and the sibling search_listings is the natural way to find one, but neither condition nor alternative is stated. No exclusions or prerequisites are given.

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