Skip to main content
Glama
TylerIlunga

Procore MCP Server

Retrieve Details For The Markup

retrieve_details_for_the_markup
Read-onlyIdempotent

Retrieve full details of a markup from Contracts or Potential Change Orders by providing the markup ID, project ID, holder type, and holder ID.

Instructions

Retrieve details for the Markup for specified holder. This endpoint supports the Contract and Potential Change Order tools. Access requires the user to have admin permissions for the relevant tool. Use this to fetch the full details of a specific Contracts by its identifier. Returns a JSON object describing the requested Contracts. Required parameters: project_id, holder_type, holder_id, id. Procore API: Construction Financials > Contracts. Endpoint: GET /rest/v1.0/financials/markups/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Contracts resource
project_idYesQuery string parameter — iD of the Markup's Project
holder_typeYesQuery string parameter — type of the Markup's Holder
holder_idYesQuery string parameter — iD of the Markup's Holder
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Beyond the annotations (readOnlyHint, etc.), the description adds that admin permissions are required and that it returns a JSON object. This provides useful behavioral context not present in annotations.

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 moderately concise but includes extraneous details like the Procore API path and endpoint, which are not essential for an agent. It front-loads the purpose but could be trimmed.

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?

The description omits information about optional parameters (page, per_page) and does not describe the JSON output structure. The inconsistent use of 'Contracts' instead of 'Markups' reduces completeness.

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 coverage is 100%, so baseline is 3. The description lists required parameters but adds no new meaning beyond the schema descriptions. It does not explain parameter relationships or constraints.

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

Purpose4/5

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

The description clearly states 'Retrieve details for the Markup' and indicates it supports Contract and Potential Change Order tools. However, it inconsistently refers to 'Contracts' instead of 'Markups', causing slight confusion.

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

Usage Guidelines2/5

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

The description mentions admin permission requirements but provides no guidance on when to use this tool versus alternatives like list or update markups. Sibling tools exist, but no differentiation is given.

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