Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Company Vendor

show_company_vendor
Read-onlyIdempotent

Retrieve full details of a specific company vendor using its ID. Returns a single JSON object with the vendor's complete field set. Read-only operation; no changes are made to Procore.

Instructions

Show detail on a specified Company Vendor. Use this when you already know which company vendor you want and need its full field set. id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the company vendor. 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: id, company_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/vendors/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Directory resource
pageNoQuery string parameter — page number for paginated results (default: 1)
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). The default view is extended.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesQuery string parameter — unique identifier for the company.
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable behavioral details: it returns a single JSON object, is read-only, and specifies common error scenarios (401, 403, 404) with their meanings. This gives the agent a clear picture of expected behavior and failure modes.

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?

The description is well-structured and information-dense, leading with the core purpose, then usage guidance, prerequisites, return type, safety, error handling, required params, and API reference. Each sentence adds value and nothing is wasted.

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 the lack of an output schema, the description compensates by stating the return type (single JSON object), error payload behavior, and the API endpoint. It also covers the prerequisite of resolving the id and the read-only nature, making it complete for an agent to decide and successfully invoke the tool.

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?

The input schema already provides full descriptions for all five parameters (100% coverage), including URL path vs query status, defaults, and enums. The description only restates the required parameters (id, company_id) without adding deeper semantics, so the baseline of 3 is appropriate.

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's function with a specific verb and resource: 'Show detail on a specified Company Vendor.' It explicitly distinguishes this from list/create/update siblings by noting it is for when you already know which vendor you want and need the full field set.

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?

The description gives explicit guidance on when to use this tool: 'Use this when you already know which company vendor you want and need its full field set.' It also instructs the agent to resolve the id with the matching list tool first, effectively naming an alternative and establishing a prerequisite workflow.

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