Skip to main content
Glama
Sign In

GrowthDept

by app.growthdept
OverviewDiscussionsAdmin

Pages GrowthDept hosts

hosted_pages
Read-onlyIdempotent

The pages GrowthDept hosts for this business at its own address, with each page's link and whether it is live or taken down. These are not the owner's own website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hosted_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare read-only, idempotent, closed-world behavior, so the description adds value by disclosing the return content (each page's link and its live/taken-down status) and its scope. It doesn't cover ordering, pagination, or how many pages come back, but the safety profile is already carried by annotations.

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 compact sentences, with the resource and scope front-loaded and the disambiguation appended as a short clarifying clause. Nothing is redundant beyond the slight restatement of the title's wording.

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?

With no parameters and no output schema, the description carries the burden of describing returns and does so at a high level (link plus status). Enough to decide whether to call it, with only minor gaps around result shape and size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter claims are made that could conflict with the empty schema.

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?

Names the specific resource (pages GrowthDept hosts for this business) and previews the returned fields (link, live or taken down). The second sentence distinguishes it from the owner's own website, separating it from website_health/check_website, though the action verb is only implicit in the noun phrase.

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 clarifying line 'These are not the owner's own website' implies the boundary against website_health and check_website, but it never states when to call this versus those siblings, and it does not mention the related take_page_down / put_page_back actions.

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

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