Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Action Plan Verification Method

show_action_plan_verification_method
Read-onlyIdempotent

Retrieve full details of a specific Action Plan Verification Method by ID. Use to get complete field data for an existing verification method in Procore.

Instructions

Details of an Action Plan Verification Method. Use this when you already know which action plan verification method you want and need its full field set. company_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the action plan verification method. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id, id. Procore API: Project Management > Action Plans. Endpoint: GET /rest/v1.0/companies/{company_id}/action_plans/verification_methods/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — action Plan Verification Method ID
company_idYesURL path parameter — unique identifier for the company.
Behavior5/5

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

Annotations already indicate read-only and non-destructive, but the description adds valuable failure-mode details (401/403/404), explicitly states it changes nothing, and confirms the return format. No contradiction with annotations.

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?

Every sentence adds distinct value: purpose, usage trigger, parameter defaults, return type, side effects, error handling, required parameters, and API endpoint. No redundancy or 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?

For a simple read-only show tool with two parameters and no output schema, the description fully covers the workflow (resolve id first), default behavior, error responses, API module, and endpoint. An agent can select and invoke this tool confidently.

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?

While the schema covers both parameters with basic descriptions, the description adds essential behavioral semantics: company_id defaults to procore_set_config value when omitted, and id must identify an existing parent record that should be resolved with the list tool first. This goes beyond the 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 clearly states the tool shows details of an Action Plan Verification Method and returns a single JSON object with the full field set. It explicitly distinguishes this from list operations by stating 'when you already know which action plan verification method you want'.

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?

Provides explicit when-to-use guidance: 'Use this when you already know which action plan verification method you want and need its full field set.' It also instructs to resolve id with the matching list tool first and explains company_id default behavior, giving clear invocation context.

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