Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Update Advance Ball In Court

update_advance_ball_in_court

Advance the ball in court for an RFI between the RFI Manager and Assignee. Updates the specified RFI record with the new ball-in-court status.

Instructions

Advances the ball in court to the specified ball in court. The RFI Manager can move ball in court between the RFI Manager and the Assignee. The Assignee can move the ball in court back to the RFI Manager, if the Assignee has responded. Use this to update an existing RFI records (only the supplied fields are changed). Updates the specified RFI records and returns the modified object on success. Required parameters: project_id, id. Procore API (v1.1): Project Management > RFI. Endpoint: PATCH /rest/v1.1/projects/{project_id}/rfis/{id}/advance_ball_in_court

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the RFI resource

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

Adds value beyond annotations by disclosing role-based permissions, partial update behavior, and the API endpoint. Does not mention what happens if conditions are not met, but overall good disclosure.

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 functional but contains some redundancy (e.g., listing required parameters already in schema). Could be slightly more concise, but information is front-loaded.

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?

Covers all necessary context: action, role permissions, partial update, success return, required parameters, and API details. Complete for a specific ball-in-court advancement 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?

Schema coverage is 100% with clear descriptions; the description redundantly lists required parameters without adding new semantics 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 advances the ball in court for an RFI, specifies roles (RFI Manager, Assignee) and conditions, and distinguishes it from many sibling tools like update_rfi.

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

Usage Guidelines4/5

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

Provides clear context on who can use the tool and under what conditions (RFI Manager vs Assignee), but does not explicitly state when not to use it or mention alternatives for other RFI updates.

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