Skip to main content
Glama

body_profile

Inspect the local machine's OS, CPU, RAM, disk, GPU, modules, agent CLIs, and speech models without installing, crawling, or uploading anything; cached locally and clearable.

Instructions

Read-only capability inventory of this machine (OS, CPU, RAM, disk, GPU, optional modules, agent CLIs, local speech models).

Nothing is installed or downloaded, nothing private is crawled, nothing is uploaded. The result is cached locally and can be cleared.

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

Input Schema

NameRequiredDescriptionDefault
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well on the safety profile: it states nothing is installed or downloaded, nothing private is crawled or uploaded, and results are cached locally and clearable. It omits cost/latency expectations and says nothing about how a refresh affects the cache, leaving the mutation-adjacent behavior of that parameter unexplained.

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 sentences, front-loaded with the core identity and the item inventory parenthetical, then a compact safety block. Dense but nearly every clause earns its place; the second sentence is a list of guarantees rather than repetition.

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?

No output schema and no annotations, so the description must cover both what comes back and the safety profile. It covers the conceptual return contents and safety well, but leaves the return format (shape, sections, units) and the refresh/cache interaction unspecified.

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

Parameters2/5

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

Schema description coverage is 0% for the single `refresh` boolean, so the description must compensate and does not: the word refresh never appears, and the only hint at caching is "the result is cached locally and can be cleared," which does not explain what setting refresh=true does versus the default cached path.

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 uses a specific verb and resource ("read-only capability inventory of this machine") and enumerates the contents (OS, CPU, RAM, disk, GPU, modules, agent CLIs, speech models), so its scope is unambiguous. It does not name or differentiate against siblings such as body_status or body_local_models, which likely overlap on machine/model information.

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: an agent gathers that this is the tool to probe hardware and installed capabilities before deciding what it can run. There is no explicit when-to-use framing, no exclusions, and no pointer to related tools when only a subset (e.g., local models) is needed.

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