Skip to main content
Glama

Agent Loopr

agentloopr_get_page

Read-onlyIdempotent

Fetch the markdown representation of a public Agent Loopr page. Pass a root-relative path such as /, /services/saas, /about, or /case-studies/blue-nelumbo.

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": {
      "path": "<path>"
    },
    "name": "agentloopr_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRoot-relative path, e.g. /services/agentic

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the meaningful constraint that only public pages are reachable (no auth), but says nothing about behavior on a missing path, caching, or how the markdown is produced.

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?

Two short sentences, front-loaded with the action and result type, then the calling convention. Slightly redundant with the schema's own path example, but nothing is wasted or padded.

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?

For a single-parameter, read-only fetch with rich annotations and no output schema, the agent knows what it gets (markdown), what it must supply (root-relative path), and the scope limit (public pages only). No material gap remains for correct invocation.

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% and the schema already defines path as a root-relative string with an example. The description restates the requirement and adds a few more example routes, which is mild reinforcement rather than new semantics (no format rules, trailing-slash behavior, or query-string handling). 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?

"Fetch the markdown representation of a public Agent Loopr page" gives a concrete verb (fetch) and a concrete resource (markdown rendering of a page), which is clearly distinct from the listing/book/get-company siblings. It stops short of explicitly naming when to prefer this over a sibling such as agentloopr_get_company, so it is clear but not differentiated by name.

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 implied rather than stated: the word "public" and the example paths suggest this is for reading site content by route, and the sibling names imply listing tools exist for enumeration. There is no explicit when-to-use, when-not-to-use, or alternative routing guidance.

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