Skip to main content
Glama
TylerIlunga

Procore MCP Server

show_app_installation

Retrieve details of a specific app installation in Procore by providing the installation ID and company or project context.

Instructions

Show app installation. [Platform - Developer Tools/App Marketplace] GET /rest/v1.0/app_installations/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp installation ID
company_idYesUnique identifier for the company. You must supply either a company_id or project_id.
project_idYesUnique identifier for the project. You must supply either a company_id or project_id.
pageNoPage number for pagination
per_pageNoItems per page (max 100)
Behavior2/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 only states 'Show app installation' and includes an HTTP GET method, implying a read-only operation, but fails to disclose behavioral traits like authentication needs, rate limits, or what data is returned. This is insufficient for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two short phrases, but it is not front-loaded with useful information. The first part is tautological, and the second part includes technical details (HTTP method) that may not be immediately helpful to an agent, making it moderately structured.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It does not explain what the tool returns, its purpose, or behavioral context, leaving significant gaps for a tool that likely retrieves installation details, which is inadequate for agent understanding.

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%, so the schema fully documents all 5 parameters. The description adds no additional parameter semantics beyond what the schema provides, which is acceptable given the high coverage, resulting in a baseline score of 3.

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

Purpose2/5

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

The description 'Show app installation' is a tautology that restates the tool name without adding clarity. It mentions a platform and HTTP method but lacks a specific verb and resource definition, making it vague about what the tool actually does (e.g., retrieve details, list installations?).

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent with no usage instructions.

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/TylerIlunga/procore-mcp-server'

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