Skip to main content
Glama

Discover the Tools

check_tool_listing

Read-onlyIdempotent

Check a public website for existing published listings before submitting. Does not reveal private pending submissions.

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": {
      "website_url": "<website_url>"
    },
    "name": "check_tool_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
website_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety bar is largely covered. The description adds real scope information beyond them: only public published listings are visible, and pending private submissions are deliberately not returned, which prevents the agent from misreading an empty result as 'nothing exists'. It does not discuss rate limits, auth, or result shape.

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?

Two short sentences, no filler, with the primary action front-loaded and the scope caveat second. Every sentence carries information the agent needs.

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?

The tool is simple and the annotations carry the safety profile, so little is strictly required. However, with no output schema and no statement of what is returned (a boolean, a listing list, or an error when nothing is found), an agent cannot predict the response shape before calling.

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 0% and the single parameter website_url has no constraint notes beyond maxLength. The description implies the parameter is the site to check, but adds no format guidance (scheme, bare domain, path handling), leaving the agent to guess how to supply the URL.

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: check a public website for existing published listings. The phrase 'before submitting' distinguishes it from the submission sibling (submit_tool), though it never names that sibling explicitly, so differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

Gives clear timing context ('before submitting'), which tells the agent when to call it in the workflow. It stops short of naming alternatives for the case it excludes ('does not reveal private pending submissions' implies get_submission_status but never says so).

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