profullstack-mcp

Get Fleet Service

fleet_get_service

Read-onlyIdempotent

Everything about one Profullstack service by domain, URL or name: surfaces, MCP endpoint, npm packages, pwamart install page, auth.

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": {
      "service": "<service>"
    },
    "name": "fleet_get_service"
  }
}

Input Schema

Name	Required	Description	Default
`service`	Yes	domain, URL or name, e.g. "hqtui.com"

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful context about the response contents, specifically surfaces, MCP endpoint, npm packages, pwamart install page, and auth, although it does not mention not-found behavior or response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted wording, and the resource and lookup keys are stated before the returned data.

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 one-parameter getter with annotations and no output schema, the description adequately explains what information is returned. Its main gap is the unresolved relationship with fleet_get_auth, which is especially relevant because auth is listed as returned data.

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?

The input schema already documents the single service parameter at 100% coverage, including the example 'hqtui.com'. The description repeats 'by domain, URL or name' but adds no matching rules, ambiguity handling, or format details beyond the 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?

The description clearly indicates a single-service lookup and enumerates the kinds of data returned: surfaces, MCP endpoint, npm packages, pwamart install page, and auth. It distinguishes itself from fleet_list_services by saying 'one' service, but its inclusion of 'auth' creates some overlap with the sibling fleet_get_auth that is not resolved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the accepted lookup keys, domain, URL, or name, but gives no guidance about when to use this tool rather than fleet_get_auth or fleet_list_services. There are no exclusions or alternative-routing instructions.

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

All profullstack-mcp tools Inspect

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

Need Help?