Skip to main content
Glama
Sign In

Toolocate

by com.toolocate
OverviewDiscussionsAdmin

Get an AI tool

get_tool
Read-onlyIdempotent

Get the full Toolocate listing of one AI tool: description, features, who it is for, FAQs, pricing plans, platforms, agent access, the official url and pageUrl, the Toolocate page to cite. checkedAt is when we last verified the official site.

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": {
      "slug": "<slug>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe tool's slug, from search_tools or from a Toolocate URL (toolocate.com/tools/<slug>/).
localeNoLanguage of the text fields and of pageUrl (default en). A tool not yet written in that language comes back in English; its locale field says which language you got.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), but the description adds value beyond them: it discloses the record's contents and explains that checkedAt is the last verification of the official site, a freshness signal an agent cannot get from the schema. It does not cover failure behavior (e.g. unknown slug) or rate limits, keeping it out of the top band.

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?

One front-loaded sentence declares the resource, then a tight comma-separated inventory of fields with no filler. The only italicised clarification, the checkedAt meaning, earns its place by defining a non-obvious field.

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?

There is no output schema, so the field enumeration in the description carries real weight, and it covers the main return surfaces including URLs and citation page. Minor gaps remain: nothing about not-found behavior or that a missing translation returns English (that is delegated to the schema).

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%, with both slug and locale fully documented in the schema, including the English fallback behavior and enum values. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource ("Get the full Toolocate listing of one AI tool") followed by an enumeration of what the record contains, which lets an agent tell it apart from a search that returns many tools. It never names a sibling explicitly, so the 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 Guidelines3/5

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

Use is only implied: fetching a slug's full record after search, and getting "the Toolocate page to cite" hints at attribution use. There is no explicit when-to-use/when-not statement or named alternative, and the slug-sourcing guidance lives in the schema description rather than here.

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

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