Skip to main content
Glama
Sign In

DexURL

by com.dexurl
OverviewDiscussionsAdmin

Save a link to the DexURL Vault

save_to_vault

Save a web address to the Vault with an optional title, folder, tags and note. Private items cannot be created here: send private: true and nothing is saved, with a pointer to the app. The Free plan holds 25 items.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe address to save (http or https).
tagsNoTags.
titleNoDefaults to the site name.
folderNoFolder name.
privateNoNot supported here: private items can only be created in the DexURL app.
descriptionNoA note about the item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint false, destructiveHint false, non-idempotent), so the bar is lower. The description does add genuinely valuable behavior: sending private: true silently saves nothing and returns a pointer instead, and titles default to the site name. It does not say what a successful save returns or whether duplicate URLs are merged, 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 short sentences, front-loaded with the action and its optional fields, then the hard constraint, then the quota. No filler. The clause 'with a pointer to the app' is slightly compressed but still readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter write tool with full schema coverage and no output schema, the definition covers the action, the silent-failure case, the metadata defaults, and the quota. The remaining gap is response behavior on success and duplicate handling, which the annotations' non-idempotent hint makes relevant.

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%, so the schema already documents every parameter including limits and the private flag. The description only adds the mapping of 'note' to the description field and reinforces optionality. Baseline 3 is correct when the schema carries the detail.

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?

The description opens with a specific verb and resource: save a web address to the Vault, plus the optional metadata it accepts. That is enough to distinguish it from read-side siblings like search_vault or get_link, but it does not explicitly contrast with create_link or add_to_bio_page, which are the nearest ambiguous alternatives.

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?

It gives a concrete exclusion and routes the agent elsewhere: private items cannot be created here, and the pointer is to the DexURL app. It also states the Free plan capacity of 25 items, which is context an agent needs before bulk-saving. What is missing is guidance on when to pick this over create_link.

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

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