Skip to main content
Glama
Sign In

Applystead

by com.applystead
OverviewDiscussionsAdmin

Read website

get_website
Read-onlyIdempotent

The member's Applystead personal website (needs an Applystead membership), for building it with the member's own agent: whether the member can have one, its address and state, the profile facts to build from, its files and one file's content. Spends no points. Actions: status, profile, list_files, read_file. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds information not in them: the membership gate and 'Spends no points', a cost signal an agent needs before calling. It also sketches the returned data per action, which matters since there is no output schema.

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 resource and the payoff data, then cost, then the action list and the help escape hatch. The opening clause is dense with parentheticals but nothing is filler.

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

Completeness3/5

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

For a tool with an opaque nested params object and no output schema, it covers what comes back and how to discover fields via help, which is the essential loop. It remains thin on what each action's params look like and offers no hint of the return shape's size or pagination for file listings.

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 50% and the params object is a free-form nested bag, so the description's list of action values (status, profile, list_files, read_file) genuinely explains the enum's meaning. However, it defers all per-action field semantics to a runtime 'help' call, adding no detail about what params should contain.

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 names a specific resource (the member's Applystead personal website) and enumerates exactly what the call surfaces: whether one can exist, its address and state, profile facts, files, and a file's content. That is far beyond restating the name, though it never names the sibling manage_website that an agent would otherwise confuse it with.

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?

It supplies a prerequisite ('needs an Applystead membership') and a purpose ('for building it with the member's own agent'), plus a discovery instruction to call action "help". It does not state when to prefer manage_website for edits, so the read-vs-write boundary is only implied.

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

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