“What’s happening with ticket 4821?” If I were adding that question to a support app, I’d give the assistant one read-only function and have the app call the ticket API. I’d revisit that choice when someone asks, “Can I look up the same ticket from my editor?”

Function calling is how a model asks an application to do something. MCP, the Model Context Protocol, gives compatible applications a common way to discover and call tools. You can use both for the same ticket lookup. And if all you need is a nightly ticket export, a scheduled API call will do.

One support app, one lookup

Give the model a tool called get_ticket that takes a ticket number. When a rep asks about ticket 4821, the model can request get_ticket(4821). Your app checks the number, calls the ticket service on the rep’s behalf, and passes the result back so the model can answer.

I’d keep that little bit of code in the support app while it’s the only caller. The team can change the tool and its caller together. This example uses a client tool, meaning your application runs it. Some providers also offer tools they execute themselves. Anthropic’s guide to tool use

A second app wants the same tool

Now an engineer wants that lookup in an editor that supports MCP. You could write another adapter. Before you do, look at what you’d have to maintain twice. When the ticket API changes how it reports a closed account, who fixes the support app? Who remembers the editor?

An MCP server can expose one get_ticket tool to both applications. Each app uses an MCP client to discover the tool and call it. The server talks to the existing ticket API. The support team gets one place to maintain the integration, and someone takes ownership of server updates, sign-in, and compatibility with both clients. MCP architecture overview

Who does what when Maya asks for ticket 4821?Follow the lookup from Maya’s question to the record she’s allowed to read.
  1. The model asksIt picks get_ticket and supplies 4821. Maya’s sign-in tells the app who is asking.
  2. The application routes the callThe support app can use its local function. With a shared integration, an MCP client sends the request to the ticket tool on the MCP server.
  3. The ticket service decidesIt checks Maya’s access to record 4821. Only an allowed result goes back for the assistant to summarize.

Try the lookup from both seats

For an accuracy check, I’d start with two fictional reps and one test ticket. Maya can read ticket 4821. Lee works for a different customer. Give both reps the same question in each client. Here’s what I’d want to see before sharing the tool more widely.

Try thisWhat to look for
Maya asks for ticket 4821She gets the right status. The service log ties the lookup to Maya and her customer account.
Lee asks for the same ticketThe service denies access. Neither client reveals the ticket title, status, or customer details.
A request contains a malformed ticket numberThe app or server rejects it before the lookup, and the rep gets a useful correction.
The ticket service times outThe rep sees that the lookup couldn’t finish. The assistant leaves the status unknown.

For each app, check which identity reached the ticket service. The service needs a trusted identity and a record-level access check. A customer ID supplied by the model can’t establish who the rep is.

I’d make the decision after that trial. If both clients work and a change to get_ticket now takes one fix, there’s a concrete reason to keep the MCP server. If the editor integration is still hypothetical, I’d ship the support app with its local function.

What changes when the tool can write?

Reading a ticket twice is usually harmless. Closing a ticket twice can send two customer notifications. If a close request times out, check whether it took effect before retrying. Decide who may close the ticket, which fields they can change, and when the rep needs to confirm. Those decisions apply to either integration.

Running model-generated code is a separate choice. A program that joins ticket updates across queues might justify a runtime with its own file, network, and credential controls. Looking up ticket 4821 takes one tool call. Code execution with MCP

DevSecOps services from Libre Labs View all posts