Share Link Resolver

List the providers the resolver supports

list_share_providers

Read-onlyIdempotent

Use this to see which drives and social platforms resolve_share_link supports before calling it, or when the user asks which links work. Returns one record per provider (id, kind, hosts, link examples, the public interface read, auth need, whether a direct URL is returned, last verified date) and the rules every adapter keeps.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_share_providers"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`rules`	Yes
`providers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare it read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful return-level context—per-provider fields including auth need, direct-URL flag, last verified date, and 'the rules every adapter keeps'—which goes beyond what annotations provide. It stops short of pagination or rate-limit details, so a 4 is fitting.

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 sentences, front-loaded with usage instructions and then a compact enumeration of return fields. Every sentence contributes directly to selection or invocation, with no filler.

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?

Given the simplicity (no parameters), rich annotations, and the presence of an output schema, the description is more than complete. It explains when to use it and what to expect, so nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the schema is empty with 100% coverage. The description correctly avoids redundant parameter discussion, so the baseline of 4 for no-param tools applies.

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 states a specific verb (see/list) and resource (drives and social platforms that resolve_share_link supports), and explicitly names the sibling tool resolve_share_link to anchor its role. An agent can immediately tell it apart from the resolver itself and other unrelated siblings.

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

Usage Guidelines5/5

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

It gives explicit when-to-use conditions: 'before calling it' (resolve_share_link) and 'when the user asks which links work'. The alternative is named directly with the selecting condition, leaving no inference required.

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

All Share Link Resolver tools Inspect

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.