aetumi

Get AETumi overview

about_aetumi

Read-onlyIdempotent

Return what AETumi is, what the platform does and its canonical links (site, docs, catalog, Labs). Platform facts only — it returns no assets, no experiences and no prices. For those use search_3d_web_assets, find_experiences or get_pricing. Read-only, no authentication, no side effects; returns public metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`links`	No	Canonical AETumi links.
`pricing`	No
`category`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "links": {
+      "description": "Canonical AETumi links.",
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "pricing": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld=false, so the safety profile is covered structurally. The description adds non-redundant context — no authentication required and the return is public metadata — which tells the agent it can call this freely without credential handling.

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?

Three tight sentences: what it returns, what it excludes plus alternatives, then the access/safety profile. Front-loaded with the payload and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail is unnecessary, and the annotations already carry the safety profile. The description covers scope, boundaries, alternatives, and auth, leaving nothing an agent needs in order to call a parameterless metadata tool correctly.

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; baseline 4 applies. The description correctly does not waste space re-explaining an empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — it returns what AETumi is, what the platform does, and its canonical links — and explicitly bounds the scope to platform facts. It also names the siblings it is not (search_3d_web_assets, find_experiences, get_pricing), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

It states when to use this tool (platform facts) and when not to (assets, experiences, prices), routing the agent explicitly to the three alternative tools for each excluded case. This is about as close to a routing table as a description gets.

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

All aetumi 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.