Skip to main content
Glama
extentos

extentos

inspectIntegration

Inspect the current Extentos integration at a project path, returning manifest, generated files status, dependency drift, and remediation gaps to see what's wired so far.

Instructions

Read-only snapshot of the current Extentos integration at a project path. Returns { found, manifest, generatedFilesStatus, dependency, drift, connectionPageConfig, gaps, summary }. found: false is NOT an error — when no extentos.manifest.json exists the call still succeeds, returning empty sub-objects plus a gaps remediation string that tells you to run generateConnectionModule. When found: true: manifest is the parsed extentos.manifest.json; generatedFilesStatus is per-file { path, exists, hasMarker, hashMatch }; dependency is { found, coordinate, file } for the Gradle/SPM dependency; drift is { fileDrift: [{ path, reason: 'missing' | 'marker_absent' | 'hash_mismatch' }], dependencyDrift: boolean }; connectionPageConfig is the committed connection-page snapshot (or null); gaps is an array of human-readable remediation strings; summary is a one-line rollup. USE before validateIntegration or for a 'what's wired so far?' read. DON'T USE for correctness checking / a pre-test gate (use validateIntegration — it severity-tiers the same surface and adds ~15 checks).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathNoAbsolute (or cwd-relative) path to the project root holding extentos.manifest.json. Optional — defaults to the MCP server's current working directory (process.cwd()); pass it explicitly whenever the project isn't the cwd.
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses that `found: false` is not an error, explains the behavior in that case (returns empty sub-objects and a `gaps` remediation string), and details all return fields. It also states read-only nature, leaving no hidden behavior.

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?

The description is well-structured with a concise opening sentence followed by a detailed breakdown using backticks and bold. It is slightly long but every sentence adds value. Could be slightly tightened, but very effective.

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?

Given no output schema, the description compensates fully by enumerating all return fields and their sub-fields with behavior. It covers all relevant scenarios (found vs not found), making the tool's complete behavior transparent. No detail is missing.

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

Parameters5/5

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

Schema coverage is 100% (projectPath). The description adds meaningful context beyond the schema: explains it's optional, defaults to cwd, and advises when to pass it explicitly. This covers syntax and usage intent.

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 opens with a clear verb-resource phrase: 'Read-only snapshot of the current Extentos integration at a project path.' It names the return structure, distinguishes from sibling validateIntegration by providing explicit usage guidance, and leaves no ambiguity about the tool's purpose.

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?

Explicitly states when to use ('USE before validateIntegration or for a 'what's wired so far?' read') and when NOT to use ('DON'T USE for correctness checking / a pre-test gate'), and names the alternative (validateIntegration) with a brief rationale. This provides clear decision criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/extentos/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server