Skip to main content
Glama
mcp-aws-explorer

mcp-aws-explorer

by hsooligan95

get_resource_detail

Retrieve full details for a single cloud resource by name from one provider's local mock dataset. Specify the provider to inspect AWS, Azure, GCP, or OCI inventory data.

Instructions

Get full details for a single resource by name, within one provider's mock dataset.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact resource name, e.g. 'demo-api-handler'
providerNoCloud provider to query: 'aws', 'azure', 'gcp', or 'oci'. All datasets are local mock data.aws

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does usefully disclose that all datasets are local mock data (relevant for the provider parameter), but says nothing about behavior when the name is not found, whether any side effects occur, or what 'full details' comprises.

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?

A single front-loaded sentence with no filler. It could be slightly crisper, but nothing is wasted.

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?

For a simple two-parameter read tool the description covers purpose and scope, and with no output schema it is not obligated to describe returns. However, with zero annotation coverage it should at least note not-found behavior or that the operation is a side-effect-free read, which it omits.

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%, including an example value for 'name' and enum values for 'provider', so the schema already does the heavy lifting. The description only reinforces that the name must be exact and the provider scopes the dataset, adding little beyond structured fields; 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?

States a specific verb ('Get') and resource ('full details for a single resource') with clear scope: one resource, matched by name, restricted to one provider's dataset. It is distinguishable from list-oriented siblings, though it never names them explicitly.

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 by 'single resource by name' (use it when you already know the name and want full detail), which contrasts implicitly with list_resources and find_idle_resources. There is no explicit when-to-use/when-not-to-use statement or reference to an alternative tool.

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