Skip to main content
Glama
Sign In

Trusoro

by com.trusoro
OverviewDiscussionsAdmin

Ask the owner to confirm a listing

request_owner_confirmation

Starts owner confirmation for a published listing. Returns confirm_url and user_code to show to the business owner (they confirm with Google or a company email), plus site_verification if you can edit the business website. Once confirmed, the API key you used here may edit the listing with update_listing if the owner allows it (or if you confirmed through the website).

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": "request_owner_confirmation"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesListing id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only mark it non-read-only, non-idempotent and non-destructive; the description goes further by naming the returned artifacts (confirm_url, user_code, site_verification), explaining what the business owner must do, and describing the permission consequence for the calling API key. It does not cover expiry, rate limits, or what happens on repeated calls for the same listing, which matters given idempotentHint=false.

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?

Three sentences, front-loaded with the action and outcome, then the return values, then the downstream permission effect. Dense but each sentence carries information; only the parenthetical about Google/company email is slightly expendable.

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?

With no output schema, the description correctly spends its words describing the return values and their purpose, and it ties the call to the follow-up update_listing capability. Nothing essential for correct invocation is missing for a one-parameter tool.

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% for the single listing_id parameter, so the schema already carries the meaning. The description adds only the constraint that the listing must be published, which is marginal but consistent with the schema.

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?

The description opens with a specific verb and resource ('Starts owner confirmation for a published listing') and clarifies the scope (published listings only). Combined with the title and the reference to update_listing, an agent can distinguish this from the sibling get_claim_status or submit_listing tools 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?

Usage is implied rather than stated: the tool applies to a published listing and is the path to gaining edit rights the API key lacks. The description explains the downstream effect with update_listing but never explicitly says when to choose this over get_claim_status or when not to call it (e.g., already-confirmed listings).

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

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