Skip to main content
Glama

Submit by Hand

Directory submission requirements

get_directory
Read-only

Everything we know about submitting to one directory: requirements, the form fields it asks for, review time, link type (dofollow / nofollow), paid options, common rejection reasons and tips. Free.

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": {
      "id": "<id>"
    },
    "name": "get_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDirectory id from search_directories.

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=true and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the payload's contents (requirements, form fields, review time, link type, paid options, rejection reasons, tips) and that access is free, which is exactly what an agent needs to plan a submission flow; it stops short of describing format or size of the response.

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?

One sentence, front-loaded with the core purpose, followed by a compact enumeration of contents and a cost note. Dense but every clause carries information; the trailing 'Free.' is slightly clipped but still useful.

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 simple read-only, single-parameter lookup with no output schema, the description tells the agent what the call yields and that it costs nothing. The only gap is error/not-found behavior and confirmation of the id prerequisite, which is minor at this complexity.

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?

With a single parameter at 100% schema coverage, the schema already explains that id is the 'Directory id from search_directories'. The description adds no meaning about the id's format, valid range, or what happens with an unknown id, so baseline 3 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?

States a specific retrieve action on a single, well-defined resource (one directory's submission requirements) and enumerates exactly what data comes back: form fields, review time, link type, paid options, rejection reasons. An agent can immediately tell this apart from search_directories, which locates ids rather than details.

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 only implied: the tool is for looking up one directory's details, and 'Free' hints there is no cost barrier. It never states when to prefer this over siblings or that a directory id must be obtained first (that ordering only appears in the schema, not the description).

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