Getting good answers
The habits that separate a useful MCP session from a frustrating one, and prompt patterns worth passing on.
Most complaints that MCP “does not work well” are really complaints about how the question was asked. These are the habits worth passing on to a client, and worth using yourself.
Name the organization#
Partner staff reach many client organizations at once, because an OAuth token carries no notion of a currently selected one. “How many open tickets?” is ambiguous. “How many open tickets does Acme have?” is not.
Ask for the shape you want#
“Give me a table of expiring contracts with the provider and end date” produces a far better answer than “check contracts”, because it tells the assistant which fields to project.
Start read-only#
Explore with questions before asking for changes. It costs nothing and builds an accurate picture in the conversation, so the eventual write is aimed at the right record.
Actually read the dry run#
It is the last checkpoint before a real write, and it is showing exactly what will change. See Changing data safely.
Use fields_describe when a field name is fuzzy#
Asking “what fields does a service have?” is faster than guessing and getting a rejection. Unknown field names are a hard error, not a silent drop.
One task per thread#
Long conversations that wander across organizations make it easy for both the person and the assistant to lose track of which record is in scope.
Prefer reports for aggregates#
“Spend by provider last quarter” through report_spend_by_provider is one bounded query. Asking the
assistant to list every invoice and add them up is slower and truncates at 100 rows per page.
Do not paste secrets#
Fields whose names look like credentials are stripped from every read, so the assistant cannot see them. Nobody should reintroduce them by hand.
Prompt patterns that work well#
| Goal | Ask it like this |
|---|---|
| Renewal exposure | ”Which contracts expire in the next 90 days, sorted by end date, with the provider name?” |
| Site audit | ”List every service and circuit at our Chicago location.” |
| Spend trend | ”Spend by provider for the first half of this year, biggest first.” |
| Invoice hunt | ”Find invoices from Lumen with status ‘disputed’.” |
| Ticket triage | ”Open tickets for Acme created this month, newest first.” |
| Careful bulk edit | ”Show me the three services missing a location, then set them to the Dallas site, one at a time, showing me each change first.” |
| Ownership | ”Who owns the Contoso renewal deal?” |
Related guides
- What an assistant can do The tool catalog, so you can answer can it do X precisely, plus how filtering, sorting, and paging work.
- Changing data safely Every write is a preview first, which fields are refused by design, and how bandwidth change orders work over MCP.
Last reviewed September 3, 2026.
Something wrong or missing? Tell us or contact support.