Skip to main content
Glama
Sign In

GEO360 Concierge

by cloud.apolloproject.geo360
OverviewDiscussionsAdmin

geo360_catalog_discovery

[Discovery Gateway] Explores the 3 Business Verticals of GEO360 (commercial_transit, luxury_vip, industrial_b2a) and transversal affiliate_2_0. Call without domain or domain='summary' for storefront; call with domain='transit', 'vip', 'b2a', or 'aff2' to enter that specific shop and retrieve its specialized tools.

Input Schema

NameRequiredDescriptionDefault
domainNoVertical shop to explore: 'summary' (3+1 vitrina), 'transit' (10 mobility tools), 'vip' (6 luxury tools), 'b2a' (12 industrial clearing tools), 'aff2' (6 arbitrage tools).summary
compactNoIf true, returns condensed schema to preserve LLM context tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / compact / description
      Previous value: -"If true, condenses output to preserve context tokens."New value: +"If true, returns condensed schema to preserve LLM context tokens."
    • changedInput schema / properties / domain / description
      Previous value: -"Domain to explore. 'summary' returns the 4-cube storefront; 'b2a', 'transit', 'vip', or 'aff2' returns that cube's cone details."New value: +"Vertical shop to explore: 'summary' (3+1 vitrina), 'transit' (10 mobility tools), 'vip' (6 luxury tools), 'b2a' (12 industrial clearing tools), 'aff2' (6 arbitrage tools)."
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "summary",
-  "b2a",
-  "transit",
-  "vip",
-  "aff2",
-  "all"
-]New value: +[
+  "summary",
+  "transit",
+  "vip",
+  "b2a",
+  "aff2",
+  "all"
+]
    • removedInput schema / properties / include_cones
      Removed value: -{
-  "default": true,
-  "description": "If true, includes details on Kappa-filtered cones and trigger vectors.",
-  "type": "boolean"
-}
  2. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain to explore. 'summary' returns the 3-cube storefront; 'b2a', 'transit', or 'vip' returns that cube's cone details."New value: +"Domain to explore. 'summary' returns the 4-cube storefront; 'b2a', 'transit', 'vip', or 'aff2' returns that cube's cone details."
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "summary",
-  "b2a",
-  "transit",
-  "vip",
-  "all"
-]New value: +[
+  "summary",
+  "b2a",
+  "transit",
+  "vip",
+  "aff2",
+  "all"
+]
  3. Added

TDQS

A3.9/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 establishes the tool as a read-only catalog/discovery gateway that returns tool listings rather than performing business operations, but it never explicitly states that no state is mutated, how the storefront summary differs from a full listing, or what the response shape looks like.

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 gateway role and followed by the invocation rule; nothing is padding. Minor jargon ('storefront') is inherited from the description rather than the schema, which slightly costs clarity.

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 2-parameter, zero-required discovery tool with no output schema, the description covers purpose, scoping, and default behavior adequately. The unexplained 'all' value and the unstated return format keep it short of complete.

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 description coverage is 100% and the enum descriptions already carry the per-domain tool counts, so the schema does the heavy lifting. The description adds only the default/omitted-parameter behavior ('Call without domain...'), and it adds nothing about 'compact' or the 'all' option.

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 ('Explores') and resource ('the 3 Business Verticals of GEO360' plus the transversal affiliate_2_0), and clarifies that entry returns 'its specialized tools'. It explicitly maps the long vertical names to the short enum codes ('transit', 'vip', 'b2a', 'aff2'), so an agent knows exactly what the tool is and how to address each scope.

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

Usage Guidelines4/5

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

It gives explicit invocation guidance: call with no domain or domain='summary' for the storefront, or with 'transit'/'vip'/'b2a'/'aff2' to enter a specific shop. The one gap is the 'all' enum value present in the schema, which the description never mentions or contrasts with 'summary'.

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

All GEO360 Concierge toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources