Skip to main content
Glama

The Very Lab

Read a page

get_page
Read-onlyIdempotent

Returns the text (Markdown) of one public page or blog article of theverylab.com. Useful pages: /manufacturing/, /services/, /faq/, /about-us/, /contact-us/.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL or path on theverylab.com, for example /faq/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value by disclosing the return medium (Markdown) and the scope restriction to public pages/blog articles, though it doesn't say what happens for a private or nonexistent path.

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 return type and scope, with example paths appended. Every clause carries information, though the 'Useful pages' list could be formatted as a scannable enumeration.

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 single-parameter read tool with full schema coverage and annotation-supplied safety hints, the description covers what the tool returns and where it applies. Error behavior on invalid or non-public paths is the only meaningful omission, and no output schema exists to carry it.

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 single url parameter is documented in-schema, so baseline 3 applies. The description adds only concrete path examples, which are helpful but do not extend meaning beyond the schema examples already present.

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?

States a specific verb and resource: returns the text of one public page of theverylab.com, with the return format (Markdown) named. It doesn't explicitly differentiate from search_site or get_company_profile, so the boundary is inferred from the 'one page' scope 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?

The 'Useful pages' list implicitly tells the agent which paths are worth fetching, but there is no explicit when-to-use versus search_site (e.g., fetch a known path vs. discover one) and no guidance on what to do if the URL is unknown.

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