Skip to main content
Glama

Little Works

get_listing_by_url

Resolve any little-works.com share URL to typed record + CTA verbs.

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": {
      "url": "<url>"
    },
    "name": "get_listing_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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; it does disclose that the tool performs polymorphic dispatch to a 'typed record' and returns 'CTA verbs', which is real behavioral value. However, it says nothing about invalid/non-little-works URLs, error behavior, permissions, or whether the call is read-only.

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 front-loaded sentence with no filler; the key output promise comes immediately. It is arguably too terse for the gaps it leaves, but nothing in it is wasted.

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 resolver with no output schema and no annotations, the description should define what a 'typed record' and 'CTA verbs' actually look like and what failure returns. It gives the shape but leaves the vocabulary undefined.

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?

One parameter at 0% schema description coverage, so the description must compensate; 'any little-works.com share URL' usefully constrains the accepted domain and format. It does not clarify whether trailing paths, query strings, or short-link variants are accepted.

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?

A specific verb ('Resolve') plus a concrete resource ('little-works.com share URL') and a stated return shape ('typed record + CTA verbs'). It is reasonably distinguishable from get_public_share_url, though the description never explicitly contrasts the two directions.

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 when-to-use context, no exclusions, and no mention of the obvious alternative (get_public_share_url) or of what happens with URLs from other domains. The agent must infer the calling context entirely from the summary sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources