[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1b6dtde378twx":3},{"_id":4,"slug":5,"title":6,"subtitle":7,"kind":8,"cards":9,"tags":58,"categories":60,"source":62,"lang":65,"author":66,"audioState":69,"stats":70,"publishedAt":73,"renderer":74},"6abad19fca21c797c7e9a544","giving-a-langchain-agent-real-world-facility-management-tool-97028242","Giving a LangChain Agent Real-World Facility-Management Tools via MCP","Most \"give your agent tools\" tutorials hand it a calculator or a weather API.","news",[10,13,18,23,28,33,38,43,48,53],{"headline":6,"body":11,"imageUrl":12,"sourceImageUrl":12},"Most \"give your agent tools\" tutorials hand it a calculator or a weather API. Useful for learning the mechanics, but it doesn't tell you what happens when an agent gets access to a real operational system — one with access control, multi-tenancy, and objects that map to actual physical things (buildings, vehicles, machines).","https:\u002F\u002Fmedia2.dev.to\u002Fdynamic\u002Fimage\u002Fwidth=1200,height=627,fit=cover,gravity=auto,format=auto\u002Fhttps%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhnjn710qv8mds6tc6e8e.png",{"headline":14,"body":15,"imageUrl":16,"images":17},"This post walks through connecting a LangChain agent","This post walks through connecting a LangChain agent to Telesherpa, an ontology-based platform for facility, fleet and field-service management, over the Model Context Protocol (MCP). By the end, the agent can query and modify real ontology objects — not toy data — using nothing but its own reasoning and the tools MCP hands it. Why this pairing is interesting Two things make this a useful example rather than a marketing demo:","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F1.webp",{"local":16},{"headline":19,"body":20,"imageUrl":21,"images":22},"The tool surface is large and role-gated. Telesherpa","The tool surface is large and role-gated. Telesherpa exposes on the order of 170 MCP tools, but which ones a given agent sees depends on its role — a public caller sees a handful of self-registration tools, an authenticated caller with the right scope sees object CRUD, reports, automation triggers, structured image filing, and more. That's a realistic shape for enterprise software, and a good stress test for whether an agent framework's tool-loading actually scales.","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F2.webp",{"local":21},{"headline":24,"body":25,"imageUrl":26,"images":27},"Onboarding requires zero human intervention. The platform is","Onboarding requires zero human intervention. The platform is self-registering: register(), activate() (a 7-digit email code), and login() are all public MCP tools. An agent can go from nothing to an authenticated session without a human ever opening a browser.","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F3.webp",{"local":26},{"headline":29,"body":30,"imageUrl":31,"images":32},"LangChain's official langchain-mcp-adapters package speaks MCP's Streamable HTTP","LangChain's official langchain-mcp-adapters package speaks MCP's Streamable HTTP transport natively, including custom headers — which is what you need for Bearer-token auth against a remote server:","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F4.webp",{"local":31},{"headline":34,"body":35,"imageUrl":36,"images":37},"That's the entire integration surface. tools is now","That's the entire integration surface. tools is now a list of LangChain-compatible tools, generated directly from the server's live tool catalog — no manual schema mapping, no maintaining a wrapper per endpoint. If Telesherpa adds a tool next week, your agent sees it next week too. Getting a token without a browser Before that snippet works you need token. Since every step is itself an MCP tool call, an agent can do this on its own:","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F5.webp",{"local":36},{"headline":39,"body":40,"imageUrl":41,"images":42},"auth_status is worth calling first in any new","auth_status is worth calling first in any new session — it tells you plainly whether your token is valid, which roles it carries, and how many of the total tools are currently visible to you. Cheaper than guessing from a 401. With tools loaded, a standard LangChain agent can now reason over real ontology objects:","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F6.webp",{"local":41},{"headline":44,"body":45,"imageUrl":46,"images":47},"Under the hood this typically resolves to a","Under the hood this typically resolves to a couple of tool calls — something like onto_type_show(\"building\") to enumerate objects, then onto_file_structured(object_id) per building to check which image categories are filled. The agent picks the sequence; you didn't hardcode it.","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F7.webp",{"local":46},{"headline":49,"body":50,"imageUrl":51,"images":52},"What makes this more than a search-and-summarize demo","What makes this more than a search-and-summarize demo is that the same tool surface supports writes: creating objects, executing defined actions on them (check-in\u002Fcheck-out, service-order creation, form submission), setting properties, and — critically for anything touching real operations — a role-based access model that determines what an agent is even allowed to attempt. The interesting engineering problem isn't \"can the agent call a tool,\" it's \"does the permission boundary hold when the caller is non-human.\"","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F8.webp",{"local":51},{"headline":54,"body":55,"imageUrl":56,"images":57},"The same MCP server works the same way","The same MCP server works the same way with CrewAI, LlamaIndex, and Microsoft's Agent Framework, since MCP is transport- and framework-agnostic by design — the tool definitions and auth flow don't change, only the client-side plumbing does. Working examples for each (some verified, some flagged as in-progress) are in telesherpa\u002Ftelesherpa-quickstarts. The full capability reference — object model, scopes, automation, structured image filing, forms — is in telesherpa\u002Fskill-telesherpa-com.","\u002Fapi\u002Fmedia\u002Fposts\u002Fgiving-a-langchain-agent-real-world-facility-management-tool-97028242\u002F9.webp",{"local":56},[59],"dev",[61],"Technology",{"name":63,"url":64},"Dev.to","https:\u002F\u002Fdev.to\u002Ftelesherpa\u002Fgiving-a-langchain-agent-real-world-facility-management-tools-via-mcp-4g1i","en",{"handle":67,"displayName":68},"spots","Spots","queued",{"views":71,"likes":72,"saves":72,"shares":72,"completions":72,"opens":72,"skips":72,"depthSum":72},3,0,"2026-09-28T20:44:15.467Z","local"]