Related Servers

Each tool has a clearly distinct role: browse categories, search endpoints, get endpoint details, execute an API call, and read/write config. Even discover_endpoints and search_endpoints both return endpoints, but their descriptions frame them as browse vs. keyword lookup, so an agent should not misselect.

All tools share a procore_ snake_case prefix and most follow a verb_noun pattern (discover_categories, get_config, search_endpoints). The one outlier is procore_api_call, which reads as noun_noun rather than call_api, but it remains clear and does not create real confusion.

Seven tools is well-scoped for a generic API-access server: discovery, search, schema inspection, execution, and config get/set each earn their place. There is no redundancy and no obvious missing companion tool.

The tool set fully covers its stated discover -> detail -> call workflow, with search added for faster lookup and config tools for context switching. Since procore_api_call can reach every Procore endpoint, no dedicated per-resource tools are needed for the server's purpose.