Skip to main content
Glama
Sign In

EverList Hub

by io.github.everlist-hq
OverviewDiscussionsAdmin

everlist_listing

One listing, full record: title, date, place, price, escrow terms, capacity, rating.

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": {
      "id": "<id>"
    },
    "name": "everlist_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYeslisting id, e.g. even-1 or jobs-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose the shape of the response (title, date, place, price, escrow terms, capacity, rating), which is real behavioral value in the absence of an output schema. It says nothing about read-only semantics, what happens when the id does not exist, or whether price/capacity are normalized values.

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?

A single dense sentence with the key concept (one listing, full record) front-loaded and no filler. It is close to under-specified rather than padded, which is the better failure mode, but the list of fields could be trimmed in favor of a note on errors or id provenance.

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?

For a one-parameter read tool with no output schema, enumerating returned fields is mostly sufficient, and annotations are absent so no safety profile is already available. Gaps remain around not-found behavior and the meaning of fields like price and escrow terms, which matter for an agent that must reason over the record.

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 id parameter is documented in the schema with concrete examples (even-1, jobs-1), so the schema does the work. The description adds no meaning beyond it, such as where ids come from or whether unknown ids error versus return empty; baseline 3 applies.

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?

"One listing, full record" plus an enumeration of the fields establishes a single-record retrieval tool, and the singular framing distinguishes it implicitly from the list-shaped sibling everlist_search. A verb is missing ("get/fetch"), so it reads as a noun phrase rather than an action, but the intent is unambiguous.

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 emphasis on "One listing" suggests this is for fetching a known record rather than browsing, which routes an agent away from everlist_search. There is no explicit when-to-use statement, no note that an id from a search result is the expected input, and no stated alternatives.

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

All EverList Hub 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